[Pan-users] Re: [0.95] Reproducible segfault when sorting on article name

[walt]

Charles Kerr wrote:
> walt wrote:
> 
>> I see that 0.96 already has this patch, and it's behavior
>> is slightly different but no better, alas:
> 
> Ha! Well, let's try again.  Here's a patch against 0.96.

Well, it's better.  Now, for example, I can sort the gmane
pan.user group by Subject and it works just fine.

But, when I go back to alt.binaries.pictures.animals on
my ISP's server and try sorting on Subject I get the same
old segfault.  I see hundreds of pairs of lines like below,
followed by the segfault:

(pan:12857): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL'
failed

(pan:12857): GLib-CRITICAL **: g_utf8_collate_key: assertion `str !=
NULL' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224321344 (LWP 12857)]
0xb7635c1f in funlockfile () from /lib/tls/libc.so.6
(gdb) bt
#0  0xb7635c1f in funlockfile () from /lib/tls/libc.so.6
#1  0xb761e55e in vfprintf () from /lib/tls/libc.so.6
#2  0xb763e377 in vasprintf () from /lib/tls/libc.so.6
#3  0xb7cfa627 in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4  0xb7ceefef in g_string_up () from /usr/lib/libglib-2.0.so.0
#5  0xb7cef07f in g_string_append_printf () from /usr/lib/libglib-2.0.so.0
#6  0xb7cde758 in g_log_default_handler () from /usr/lib/libglib-2.0.so.0
#7  0xb7cddbfa in g_logv () from /usr/lib/libglib-2.0.so.0
#8  0xb7cddd86 in g_log () from /usr/lib/libglib-2.0.so.0
#9  0xb7cdddec in g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0
#10 0xb7cf5230 in g_utf8_casefold () from /usr/lib/libglib-2.0.so.0
#11 0x080ba5b2 in (anonymous namespace)::do_collate (address@hidden)
at header-pane.cc:81
#12 0x080ba7b7 in (anonymous namespace)::get_collated_subject
(model=0x8b38138, iter=0x8b8daf0)
    at string-view.h:147
#13 0x080ba80e in (anonymous namespace)::get_collated_subject
(model=0x8b38138, iter=0x8b8daf0)
    at header-pane.cc:110
#14 0x080ba80e in (anonymous namespace)::get_collated_subject
(model=0x8b38138, iter=0x8b8daf0)
    at header-pane.cc:110
<the line above, repeated thousands of times>

Maybe try printing some debugging statements inside that loop?
I'd be happy to try anything you suggest.