GNOME Bugzilla – Bug 147300
crash when open a gossip log file
Last modified: 2009-08-15 18:40:50 UTC
$ gedit somebody@jabber.org the gedit windows pops up, but crashes before I can do any operation. -------------------------------------------------------------------- Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1092932640 (LWP 6937)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40bd040e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 48469
the exact version is 2.6.1-1 from debian.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. Secondly, any information you can give about the file you were trying to load would be great. Size details of the file using: wc `filename` and whether or not the file contains characters from languages other then english (for example chinese characters).
It seems a crash in gtksourceview. But as Davyd wrote the attached stack trace is not very useful in determining the cause of the crash.
It's weird that I can not reproduce the crash now. Same log file, same gedit binary, it loads just fine. On the other day, it crashed every time. Yes, the log contains Chinese characters, presumably in UTF-8 encoding. xwang@gosling:~/.gnome2/Gossip/logs$ file xxx\@jabber.com.cn.log xxx@jabber.com.cn.log: XML document text xwang@gosling:~/.gnome2/Gossip/logs$ ls -l xxx\@jabber.com.cn.log -rw-r--r-- 1 xwang xwang 412194 Jul 12 19:36 xxx@jabber.com.cn.log xwang@gosling:~/.gnome2/Gossip/logs$ wc xxx\@jabber.com.cn.log wc: gwh@jabber.com.cn.log:11: Invalid or incomplete multibyte or wide character wc: gwh@jabber.com.cn.log:14: Invalid or incomplete multibyte or wide character ... ... I'm not sure why wc complained. Maybe wc cannot handle multibyte characters. firefox displays the log file without any problem. Also, 'iconv -f utf8 -t gb2312 xxx@jabber.com.cn.log > gb2312.txt' runs just fine.
Closing since the reported is no more able to reproduce it and the attached stack trace does not contain debugging symbols.