gs crashed with SIGSEGV in gs_gc_reclaim()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ghostscript (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ghostscript
i will print out a *.pdf file. this fil was made whit OO on karmic. on a second pc
ProblemType: Crash
Architecture: i386
CupsErrorLog:
Date: Thu Nov 5 14:05:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gs
Lpstat:
device for faxprinter: socket:
device for HP-LaserJet-6L: hp:/par/
MachineType: Foxconn OEM
NonfreeKernelMo
Package: ghostscript 8.70.dfsg.
Papersize: a4
PpdFiles: HP-LaserJet-6L: HP LaserJet 6L Foomatic/ljet4 (recommended)
ProcCmdLine: root=UUID=
ProcCmdline: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -sDEVICE=ljet4 -dDEVICEWIDTHPO
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xa0bd45: mov (%ecx),%eax
PC (0x00a0bd45) ok
source "(%ecx)" (0xbfd1451e) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ghostscript
StacktraceTop:
?? () from /usr/lib/libgs.so.8
?? () from /usr/lib/libgs.so.8
?? () from /usr/lib/libgs.so.8
gs_gc_reclaim () from /usr/lib/libgs.so.8
?? () from /usr/lib/libgs.so.8
Title: gs crashed with SIGSEGV in gs_gc_reclaim()
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 12/12/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: P4M900-8237A
dmi.board.vendor: Foxconn
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: OEM
dmi.sys.vendor: Foxconn
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #361239, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.