GNOME Bugzilla – Bug 374155
Crashes when opening svgz document
Last modified: 2007-01-24 11:36:24 UTC
Steps to reproduce: 1. Open eog 2. File > Open file 3. eog exits Stack trace: [pid 13193] 22:39:30.650351 read(17, "A", 1) = 1 [pid 13193] 22:39:30.650481 writev(13, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12 [pid 13193] 22:39:30.650975 close(13) = 0 [pid 13193] 22:39:30.651214 futex(0x80c8db4, FUTEX_WAKE, 1 <unfinished ...> [pid 13188] 22:39:30.651301 <... futex resumed> ) = 0 [pid 13188] 22:39:30.651367 futex(0x80c8db0, FUTEX_WAIT, 2, NULL <unfinished ...> [pid 13193] 22:39:30.651455 <... futex resumed> ) = 1 [pid 13193] 22:39:30.651519 futex(0x80c8db0, FUTEX_WAKE, 1 <unfinished ...> [pid 13188] 22:39:30.651586 <... futex resumed> ) = 0 [pid 13188] 22:39:30.651648 futex(0x80c8db0, FUTEX_WAKE, 1) = 0 [pid 13188] 22:39:30.651735 futex(0x80c8c38, FUTEX_WAKE, 1) = 0 [pid 13188] 22:39:30.653646 exit_group(0) = ? [pid 13193] 22:39:30.653757 <... futex resumed> ) = 1 [pid 13198] 22:39:30.653824 <... futex resumed> ) = -1 EINTR (Interrupted system call) Other information: Here is the file that crashes eog: http://www.ubalt.edu/bnia/Axiomap/c_data/svg_asv.svgz I got the file from: http://www.ubalt.edu/bnia/Axiomap/c_data/index.htm Download it somewhere and open with eog. The image is supposed to show an interactive map of Baltimore, probably including crime data and "vital signs" (see http://www.ubalt.edu/bnia/mapping/statistical.html ) Note: I couldn't copy-paste the whole strace file. I try to upload it.
Created attachment 76415 [details] strace of crash
Created attachment 76416 [details] backtrace of crash
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Could you please let me know which elements are missing exactly (package names :) )? I used https://wiki.ubuntu.com/DebuggingProgramCrash (I'm using Dapper, so I followed "Old Notes" in that page) to get the debugging version of eog.
sebastien, can you please answer towsonu's question? thanks in advance.
from the "backtrace": "Program exited normally. (gdb) backtrace No stack." dapper has no eog debug package, you need to build one
(In reply to comment #6) > from the "backtrace": > > "Program exited normally. > (gdb) backtrace > No stack." > > dapper has no eog debug package, you need to build one > I did, using the "Old Notes" from https://wiki.ubuntu.com/DebuggingProgramCrash Maybe the problem is bc the program seems to exit normally while in fact it is crashing?
I still need to know which devel packages to install to give feedback if you need it :)
Confirming. (In reply to comment #7) > Maybe the problem is bc the program seems to exit normally while in fact it is > crashing? > You seem to be right here. EOG simply quits so you would have to break on gtk_main_quit() to (hopefully) see why it's quitting. It appears to me that the mechanism which quits EOG when opening an unsupported file from the command line. It's possibly triggered because there is something wrong with that file (there seem to be problems to recognize the compression), but it's reproducable with other unsupported files as well.
This should be fixed in SVN trunk now (rev. 3489): 2007-01-24 Claudio Saavedra <> * shell/main.c: (job_prepare_model_finished): Show an error message instead of closing the program if the image loading has failed. Fixes bug #399988. It still doesn't open the .svgz file but that is another problem (bug 394803). Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report. *** This bug has been marked as a duplicate of 399988 ***