After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 111435 - 0.13.95 segfault
0.13.95 segfault
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.14.0 betas
Other All
: Normal normal
: 0.14.0
Assigned To: Charles Kerr
Pan QA Team
: 111432 111444 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-04-23 16:25 UTC by Charles Kerr
Modified: 2006-06-18 05:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Kerr 2003-04-23 16:25:14 UTC
From: "Dave C." <devchan1@bellsouth.net>

Hi,
        I am using pan 0.13.95. Kernel 2.4.20, glibc 2.2.5, gtk 2.2,         
glib 2.2. Pan is segfaulting and I don't know why. I am including the         
backtrace script so you guys can trouble shoot.
Comment 1 Charles Kerr 2003-04-23 16:26:25 UTC
i:Exit  -:PrevPg  <Space>:NextPg  ?:Help                             
                 (gdb) info threads^M
  8 Thread 6151 (LWP 28223)  0x406d4ba1 in nanosleep () from
/lib/libc.so.6^M
  7 Thread 5126 (LWP 28222)  0x406f7d94 in read () from /lib/libc.so.6^M
* 6 Thread 4101 (LWP 28221)  0x4062829d in pthread_mutex_lock ()^M
   from /lib/libpthread.so.0^M
  5 Thread 3076 (LWP 28220)  0x406f7d94 in read () from /lib/libc.so.6^M
  4 Thread 2051 (LWP 28219)  0x406f7d94 in read () from /lib/libc.so.6^M
  3 Thread 1026 (LWP 28218)  0x406f7d94 in read () from /lib/libc.so.6^M
  2 Thread 2049 (LWP 28217)  0x406fd3e2 in poll () from /lib/libc.so.6^M
  1 Thread 1024 (LWP 28216)  0x40660791 in sigsuspend () from
/lib/libc.so.6^M
(gdb) thread 1^M
[Switching to thread 1 (Thread 1024 (LWP 28216))]#0  0x40660791 in
sigsuspend^M
    () from /lib/libc.so.6^M
(gdb) bt^M
  • #0 sigsuspend
    from /lib/libc.so.6^M
  • #1 __pthread_wait_for_restart_signal
  • #2 __pthread_alt_lock
    from /lib/libpthread.so.0^M
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0^M
  • #0 poll
    from /lib/libc.so.6^M
  • #1 __pthread_manager
    from /lib/libpthread.so.0^M
  • #2 __pthread_manager_event
    from /lib/libpthread.so.0^M
  • #0 read
    from /lib/libc.so.6^M
  • #1 __JCR_LIST__
    from /lib/libpthread.so.0^M
  • #2 g_io_unix_read
    from /usr/local/lib/libglib-2.0.so.0^M
  • #0 read
    from /lib/libc.so.6^M
  • #1 __JCR_LIST__
    from /lib/libpthread.so.0^M
  • #2 g_io_unix_read
    from /usr/local/lib/libglib-2.0.so.0^M
The program is running.  Exit anyway? (y or n) y^M
dave:~/$
Script done on Wed Apr 23 11:02:28 2003
Comment 2 Charles Kerr 2003-04-23 16:28:49 UTC
Program received signal SIGSEGV, Segmentation fault.^M
[Switching to Thread 4101 (LWP 28221)]^M
0x4062829d in pthread_mutex_lock () from /lib/libpthread.so.0^M      
      
(gdb) bt^M              
  • #0 pthread_mutex_lock
    from /lib/libpthread.so.0^M
  • #1 free
    from /lib/libc.so.6^M
  • #2 g_free
    from /usr/local/lib/libglib-2.0.so.0^M
  • #3 decode_article
    at decode.c line 361
  8 Thread 6151 (LWP 28223)  0x406d4ba1 in nanosleep () from
/lib/libc.so.6^M
  7 Thread 5126 (LWP 28222)  0x406f7d94 in read () from /lib/libc.so.6^M
* 6 Thread 4101 (LWP 28221)  0x4062829d in pthread_mutex_lock ()^M
   from /lib/libpthread.so.0^M
  5 Thread 3076 (LWP 28220)  0x406f7d94 in read () from /lib/libc.so.6^M
  4 Thread 2051 (LWP 28219)  0x406f7d94 in read () from /lib/libc.so.6^M
  3 Thread 1026 (LWP 28218)  0x406f7d94 in read () from /lib/libc.so.6^M
  2 Thread 2049 (LWP 28217)  0x406fd3e2 in poll () from /lib/libc.so.6^M
  1 Thread 1024 (LWP 28216)  0x40660791 in sigsuspend () from
/lib/libc.so.6
Comment 4 Charles Kerr 2003-04-23 16:33:43 UTC
eh, what crack am I smoking, this isn't fixed ...
Comment 5 Charles Kerr 2003-04-23 16:35:06 UTC
D'oh!  I thought I'd closed it by accident ... Chris, tell me you were
working on that already, and didn't actually fix it in the three
minutes between the time I submitted the ticket and you marked it as
fixed... :)
Comment 6 Christophe Lambin 2003-04-23 16:36:22 UTC
:)

I fixed this yesterday. No, I'm not _that_ fast. :)
Comment 7 Christophe Lambin 2003-04-23 18:06:37 UTC
*** Bug 111444 has been marked as a duplicate of this bug. ***
Comment 8 Charles Kerr 2003-04-23 22:24:22 UTC
*** Bug 111432 has been marked as a duplicate of this bug. ***