[Bug 28640] GTK2 apps crash when browsing a directory with UTF8 filenames

Billy Kwong tuppa at tuppa.org
Tue Jan 17 22:55:33 UTC 2006


Public bug report changed:
https://launchpad.net/malone/bugs/28640

Comment:
Ok, did more poking around, it seems that the problem is not in glib,
but in libc6.

As I went into the directory in question in bash, ls did not seem to
have the problem. But once I attempt to use command line completion on
one particular directory with an UTF8 encoded name, blammo.

The following is a backtrace from bash (using libc6-dbg):

Program received signal SIGSEGV, Segmentation fault.
0xb7e0383f in *__GI___strcoll_l (s1=0x1 <Address 0x1 out of bounds>,
    s2=0x81b7d68 "LOVE 05 \uffff\203\205\uffff\uffff\214\uffff\233\206", l=0x2e35cc)
    at strcoll_l.c:412
412     strcoll_l.c: No such file or directory.
        in strcoll_l.c
(gdb) bt
#0  0xb7e0383f in *__GI___strcoll_l (s1=0x1 <Address 0x1 out of bounds>,
    s2=0x81b7d68 "LOVE 05 \uffff\203\205\uffff\uffff\214\uffff\233\206", l=0x2e35cc)
    at strcoll_l.c:412
#1  0xb7dffeb6 in *__GI_strcoll (s1=0x2e35cc <Address 0x2e35cc out of bounds>,
    s2=0x2e35cc <Address 0x2e35cc out of bounds>) at strcoll.c:37
#2  0xb7dc3ab3 in msort_with_tmp (b=0x819e3cc, n=2, s=4,
    cmp=0x80c10f1 <_rl_qsort_string_compare>, t=0xbfe241b0 "4") at msort.c:56
#3  0xb7dc3c4c in *__GI_qsort (b=0x819e3cc, n=2, s=4,
    cmp=0x80c10f1 <_rl_qsort_string_compare>) at msort.c:102
#4  0x080b8ca0 in rl_filename_completion_function ()
#5  0x080b91ec in rl_complete_internal ()
#6  0x080b2fe2 in _rl_dispatch_subseq ()
#7  0x080b332e in _rl_dispatch ()
#8  0x080b33c6 in readline_internal_char ()
#9  0x080b350a in readline ()
#10 0x0805eae4 in yy_input_name ()
#11 0x08060cc1 in execute_prompt_command ()
#12 0x08061e01 in execute_prompt_command ()
#13 0x08064c92 in yyparse ()
#14 0x0805e564 in parse_command ()
#15 0x0805e602 in read_command ()
#16 0x0805e77f in reader_loop ()
#17 0x0805e314 in main ()

More of an administrative question, how do I reassign the source package
of an existing bug?




More information about the desktop-bugs mailing list