Crash after SIGABRT

Bug #249444 reported by mehturt
10
Affects Status Importance Assigned to Milestone
xpdf (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Xpdf crashes, gdb backtrace is:
Program received signal SIGABRT, Aborted.
0x00007fc9a5900095 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007fc9a5900095 in raise () from /lib/libc.so.6
#1 0x00007fc9a5901af0 in abort () from /lib/libc.so.6
#2 0x00007fc9a5944f5c in ?? () from /lib/libc.so.6
#3 0x00007fc9a5945bb7 in free () from /lib/libc.so.6
#4 0x00007fc9a65f71c2 in ?? () from /usr/lib/libX11.so.6
#5 0x00007fc9a75f03d2 in XpmCreatePixmapFromData () from /usr/lib/libXm.so.2
#6 0x000000000049d87a in ?? ()
#7 0x00000000004a13a1 in ?? ()
#8 0x0000000000494ca2 in ?? ()
#9 0x00000000004a55a8 in ?? ()
#10 0x00007fc9a58ec1c4 in __libc_start_main () from /lib/libc.so.6
#11 0x0000000000406369 in ?? ()
#12 0x00007fffafffe4a8 in ?? ()
#13 0x0000000000000000 in ?? ()

Looks similar to bug 9820.
I'm using Hardy on x86_64. Let me know what other details should I supply.

Revision history for this message
Diwaker Gupta (diwaker) wrote :

I can confirm this on Intrepid under KDE 4.2. I get the exact same backtrace as the OP, repeated here for completeness:

Program received signal SIGABRT, Aborted.
0x00007fd1bb131015 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007fd1bb131015 in raise () from /lib/libc.so.6
#1 0x00007fd1bb132b83 in abort () from /lib/libc.so.6
#2 0x00007fd1bb177a80 in ?? () from /lib/libc.so.6
#3 0x00007fd1bbe48cf2 in ?? () from /usr/lib/libX11.so.6
#4 0x00007fd1bce42f32 in XpmCreatePixmapFromData () from /usr/lib/libXm.so.2
#5 0x00000000004a3baa in ?? ()
#6 0x00000000004a7cd8 in ?? ()
#7 0x0000000000499fe2 in ?? ()
#8 0x00000000004aae2a in ?? ()
#9 0x00007fd1bb11c466 in __libc_start_main () from /lib/libc.so.6
#10 0x00000000004065b9 in ?? ()
#11 0x00007fffc585fca8 in ?? ()
#12 0x000000000000001c in ?? ()
#13 0x0000000000000002 in ?? ()
#14 0x00007fffc5860743 in ?? ()
#15 0x00007fffc5860755 in ?? ()
#16 0x0000000000000000 in ?? ()

I've marked #322900 as a duplicate, since the problems seem identical.

Revision history for this message
Michael Gilbert (michael-s-gilbert) wrote :

is this still a problem with 3.02-9? are there particular files or actions that cause this?

Revision history for this message
mehturt (mehturt) wrote :

No, I did not see this in a while..

Changed in xpdf (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.