After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 114793 - Crash when loading bad postscript file
Crash when loading bad postscript file
Status: VERIFIED INCOMPLETE
Product: GGV
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Jaka Mocnik
Jaka Mocnik
Depends on:
Blocks:
 
 
Reported: 2003-06-09 19:10 UTC by David Bourguignon
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Bourguignon 2003-06-09 19:08:41 UTC 
Package: GGV
Severity: blocker
Version: 1.99.9
Synopsis: Crash when loading bad postscript file
Bugzilla-Product: GGV
Bugzilla-Component: GGV
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
Crash when loading bad postscript file.

Steps to reproduce the problem:
1. Load bad postscript file.
2.
3.

Actual Results:
Crash.

Expected Results:
Read bad postscript file (gv actually manages to do it!).

How often does this happen?
Each time the bad postscript file is loaded.

Additional Information:
Example of bad postscript file:
http://www.cs.cmu.edu/~quake-papers/painless-conjugate-gradient.ps



Debugging Information:

Backtrace was generated from '/usr/bin/ggv'

(no debugging symbols found)...[New Thread 8192 (LWP 22717)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 37619

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_datalist_id_get_data
    at gdataset.c line 461
  • #7 g_object_notify_queue_freeze
    at gobjectnotifyqueue.c line 71
  • #8 g_object_newv
    at gobject.c line 734
  • #9 g_object_new_valist
Comment 1 Elijah Newren 2003-07-08 15:32:14 UTC 
Works fine here on the postscript file you mention using both ggv
version 1.99.98 and version 2.3.1.  Can you duplicate this bug?  If
so, can you try a newer version and see if you still get the error? 
If you still get the error, can you submit a better stack trace (the
one you submitted appears to have been truncated)?
Comment 2 Elijah Newren 2003-07-10 16:28:34 UTC 
From email:

  I have serious troubles reading postscript files on my machine right
  now... I think the problem I encountered with ggv is mostly due to my
  installation rather than to ggv itself.  Sorry for the disturbance.

No problem--thanks for following up.  I'm closing.