[Pan-users] Pan 0.13.2.90 Crashing Here

[John J. LeMay Jr.]

Just built and installed 0.13.2.90 here, and I'm unable to post, reply, follow
up, etc. When I try, Pan segfaults. I attached a backtrace, however when I did
the backtrace Pan caught a breakpoint when I tried to load a group. I didn't
even get to open a new message window.

Here's the end of a runlog in case it helps:

(      nntp.c:93:   nntp_get_response)(thread 0x819f368)(time 04:44:43)(depth  
3) TRACE: - nntp_get_response
(task-headers.c:462:task_get_header_range)(thread 0x819f368)(time
04:44:43)(depth   2) TRACE: - task_get_header_range
(task-headers.c:366:    task_headers_run)(thread 0x819f368)(time
04:44:43)(depth   1) TRACE: - task_headers_run
(status-item.c:185:status_item_set_active)(thread 0x819f368)(time
04:44:43)(depth   2) TRACE: + status_item_set_active
(      gui.c:694:status_item_active_changed_cb)(thread 0x819f368)(time
04:44:43)(depth   3) TRACE: + status_item_active_changed_cb
(      gui.c:711:status_item_active_changed_cb)(thread 0x819f368)(time
04:44:43)(depth   2) TRACE: - status_item_active_changed_cb
(status-item.c:193:status_item_set_active)(thread 0x819f368)(time
04:44:43)(depth   1) TRACE: - status_item_set_active
(   queue.c:1246:      socket_cleanup)(thread 0x819f368)(time 04:44:43)(depth  
2) TRACE: + socket_cleanup
(   queue.c:1306:      socket_cleanup)(thread 0x819f368)(time 04:44:43)(depth  
1) TRACE: - socket_cleanup
(    queue.c:203:        queue_wakeup)(thread 0x819f368)(time 04:44:43)(depth  
2) TRACE: + queue_wakeup
(    queue.c:217:        queue_wakeup)(thread 0x819f368)(time 04:44:43)(depth  
1) TRACE: - queue_wakeup
(   queue.c:1429:       queue_do_todo)(thread 0x819aa48)(time 04:44:43)(depth  
1) TRACE: + queue_do_todo
(   queue.c:1246:      socket_cleanup)(thread 0x819aa48)(time 04:44:43)(depth  
2) TRACE: + socket_cleanup
(   queue.c:1306:      socket_cleanup)(thread 0x819aa48)(time 04:44:43)(depth  
1) TRACE: - socket_cleanup
(    queue.c:203:        queue_wakeup)(thread 0x819aa48)(time 04:44:43)(depth  
2) TRACE: + queue_wakeup
(    queue.c:217:        queue_wakeup)(thread 0x819aa48)(time 04:44:43)(depth  
1) TRACE: - queue_wakeup
(   queue.c:1485:       queue_do_todo)(thread 0x819aa48)(time 04:44:43)(depth  
0) TRACE: - queue_do_todo
(   queue.c:1171:queue_run_what_we_can)(thread 0x819aa48)(time 04:44:43)(depth 
1) TRACE: + queue_run_what_we_can
(   queue.c:1236:queue_run_what_we_can)(thread 0x819aa48)(time 04:44:43)(depth 
0) TRACE: - queue_run_what_we_can done
(   queue.c:1429:       queue_do_todo)(thread 0x819aa48)(time 04:44:43)(depth  
1) TRACE: + queue_do_todo
(   queue.c:1485:       queue_do_todo)(thread 0x819aa48)(time 04:44:43)(depth  
0) TRACE: - queue_do_todo
(   queue.c:1171:queue_run_what_we_can)(thread 0x819aa48)(time 04:44:43)(depth 
1) TRACE: + queue_run_what_we_can
(   queue.c:1236:queue_run_what_we_can)(thread 0x819aa48)(time 04:44:43)(depth 
0) TRACE: - queue_run_what_we_can done
(      gui.c:651:gui_remove_status_item_idle)(thread 0x817e788)(time
04:44:43)(depth   1) TRACE: + gui_remove_status_item
(status-item-view.c:307:status_item_view_set_item_nolock)(thread
0x817e788)(time 04:44:43)(depth   2) TRACE: + status_item_view_set_item_nolock
(status-item-view.c:351:status_item_view_set_item_nolock)(thread
0x817e788)(time 04:44:43)(depth   1) TRACE: - status_item_view_set_item_nolock
(      gui.c:667:gui_remove_status_item_idle)(thread 0x817e788)(time
04:44:43)(depth   0) TRACE: - gui_remove_status_item
Segmentation fault

-- 
John LeMay
Senior Enterprise Consultant
NJMC | http://www.njmc.com | Phone 732-557-4848
Specializing in Microsoft and Unix based solutions

pan_backtrace
Description: Text document