GNOME Bugzilla – Bug 146575
Program crash when opening pdf file
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Gentoo Base System version 1.4.16 Package: gpdf Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Gentoo Linux Synopsis: Program crash when opening pdf file Bugzilla-Product: gpdf Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Program crashed when opening the following PDF file: http://people.redhat.com/drepper/dsohowto.pdf Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: The version of gnome-pdf-viewer is 0.131 The OS is Gentoo Linux, running on an Athlon 1800 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 03:09 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gpdf". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was ta@taydin.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
Created attachment 29388 [details] The dialog that pops up when the problem occurs When I run gpdf with the dsohowto.pdf file as an argument, this dialog box pops up.
Created attachment 29389 [details] The gdb session This is the gdb session that I did in order to get a stack trace. However, the debugger doesn't get control and the problem is notified with a dialog box. It is strange that the debugger doesn't catch a crash, even though I have told the debugger to stop after receiving any signal. Maybe this isn't a crash, but instead gpdf detects an error condition and decides that it cannot continue.
Hmmm. Odd. Okay, I'll reopen for the maintainer to look at. :)
The stack is the following: (gdb) bt
+ Trace 48597
This bug is fixed post 0.131... *** This bug has been marked as a duplicate of 139211 ***