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
while opening a pdf
ProblemType: Crash
Architecture: i386
Date: Tue Nov 10 11:23:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gs
Lpstat:
device for ColorLaserJet3600n: hp:/net/
device for LaserJet3005dn: hp:/net/
device for Stylus_CX3200: usb://EPSON/
MachineType: Hewlett-Packard HP Compaq 6710b (KE121ET#ABE)
Package: ghostscript 8.70.dfsg.
Papersize: a4
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PpdFiles:
LaserJet3005dn: HP LaserJet P3005 Postscript (recommended)
Stylus_CX3200: Epson Stylus CX3200 - CUPS+Gutenprint v5.2.4 Simplified
ColorLaserJet3
ProcCmdLine: root=UUID=
ProcCmdline: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=
ProcEnviron:
PATH=(custom, no user)
LANG=es_ES.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x3c5d45: mov (%ecx),%eax
PC (0x003c5d45) ok
source "(%ecx)" (0xbef7b3ce) 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: 04/10/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.11
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 6710b (KE121ET#ABE)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.