GNOME Bugzilla – Bug 382420
Crashes when I hit save
Last modified: 2006-12-14 16:26:39 UTC
Steps to reproduce: 1. Open Bluefish. 2. Type or don't type anything 3. Click save or save as... Stack trace: Memory status: size: 56803328 vsize: 0 resident: 56803328 share: 0 rss: 16879616 rss_rlim: 0 CPU usage: start_time: 1165271042 rtime: 0 utime: 104 stime: 0 cutime:98 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/bluefish' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) (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 -1227266384 (LWP 5065)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 91628
Thread 1 (Thread -1227266384 (LWP 5065))
Other information:
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!
Stack Trace above was copy pasted from Bug Buddy. Did another one using GDB and this has more info. The program Segfaulted with this output: **************************************************** Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1226537296 (LWP 9312)] 0x08071e27 in ?? () ***************************************************** Here is the stack trace: *****************************************************
+ Trace 92348
Thread 3 (Thread -1251271776 (LWP 9330))
Hope this helps
sigh, unfortunately that stacktrace is not helpful either. :-( which distribution and which version are you using?
Yea sorry about that, I started realizing that as I read more on stack traces. I am using Ubutnutu Edgy and bluefish 1.0.6. I am still trying to get a better stack trace. If you want me to try anything or have a suggestion to get more information please let me know.
yeah, unfortunately there are no debug packages for bluefish provided by ubuntu, so i'd kindly ask you to install debug packages for the basic gnome libraries, like libgtk2.0-0-dbg and libglib2.0-0-dbg. don't know if that will help us here, though. :-/
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Ask the Ubuntu MOTUs for an updated package. The fix is already mentioned in the related launchpad-entry [1] and bluefish 1.0.7 already contains the fix. JFTR: There is no better way for a bluefish stacktrace. It strips the executable by default (only in stable version). And during the (Debian) packaging process, the executable is stripped too via dh_strip. It needs knowledge about Debian packages [1] and a small "hack" in src/Makefile(.in) (remove the '-s' option in INSTALL_PROGRAM) to get a meaningful backtrace. A bluefish-dbg package would be bloat atm and because Etch is near, it doesn't make sense to block bluefish updates/fixes with a new bluefish-dbg package in NEW. I will add one for the current development version. IMHO better describe how to reproduce the issue and we can care about the backtrace without the necessity to rebuild any package. [1] https://launchpad.net/distros/ubuntu/+source/bluefish/+bug/64016 [2] http://wiki.debian.org/HowToGetABacktrace *** This bug has been marked as a duplicate of 360401 ***