GNOME Bugzilla – Bug 134693
Invalid header, Null, seg fault
Last modified: 2004-12-22 21:47:04 UTC
I've been getting this error for months on Pan 0.14.2, both in Windows XP Home and in Linux, both RH 9 and Fedora Core 1. About 1 in 20 jpeg images in various newsgroups will crash Pan, leaving the message: (Null) - Invalid header: These same images will load into Mozilla with no problem. Here is the requested trace as described on the Pan web site: " Script started on Tue Feb 17 19:48:21 2004 /home/rlc% uname -a^M Linux dhcp-68-24.ece.rice.edu 2.6.2 #1 Thu Feb 12 16:09:27 CST 2004 i686 i686 i386 GNU/Linux /home/rlc% setenv LD_ASSUME KERNEL 2.4.1^M /home/rlc% gdb pan^M GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) handle SIGUSR1 nostop noprint Signal Stop Print Pass to program Description SIGUSR1 No No Yes User defined signal 1 (gdb) handle SIG32 nostop noprint Signal Stop Print Pass to program Description SIG32 No No Yes Real-time event 32 (gdb) run Starting program: /usr/bin/pan (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 10087)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 32769 (LWP 10102)] [New Thread 16386 (LWP 10103)] [New Thread 32771 (LWP 10104)] [New Thread 49156 (LWP 10105)] [New Thread 65541 (LWP 10106)] [New Thread 81926 (LWP 10107)] [New Thread 98311 (LWP 10108)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 114696 (LWP 10109)] [New Thread 131080 (LWP 10110)] (no debugging symbols found)... (no debugging symbols found)...(Null) - Invalid header: (no debugging symbols found)... (no debugging symbols found)...(Null) - Invalid header: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 98311 (LWP 10108)] 0x4010ad5c in memcpy () from /lib/i686/libc.so.6 (gdb) thread apply all bt
+ Trace 44286
Thread 8 (Thread 98311 (LWP 10108))
The program is running. Exit anyway? (y or n) y /home/rlc% ^ Script done on Tue Feb 17 19:50:02 2004 " I'd be happy to work with someone to identify the bug. I tracked it into the Pan source, and the header is indeed null, but couldn't proceed since I don't know Gtk. Randy
Fixed in beta 0.14.2.91. *** This bug has been marked as a duplicate of 125051 ***