GNOME Bugzilla – Bug 378825
Crashes when attempting to "add" an empty "mispelled word" field
Last modified: 2007-07-06 02:43:22 UTC
Spell checker works fine, but when I click the "add" button in the spellcheck menu (to add a dictionary), Bluefish crashes instantly. I use Bluefish on Ubuntu 6.10 (completely standard install), editing html files only. Memory status: size: 40435712 vsize: 0 resident: 40435712 share: 0 rss: 16990208 rss_rlim: 0 CPU usage: start_time: 1164374053 rtime: 0 utime: 166 stime: 0 cutime:157 cstime: 0 timeout: 9 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 -1226856784 (LWP 4723)] (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 89016
Thread 1 (Thread -1226856784 (LWP 4723))
(In reply to comment #0) > Spell checker works fine, but when I click the "add" button in the spellcheck > menu (to add a dictionary), Bluefish crashes instantly. The "Add" button does not add a dictionary. It adds a word to a dictionary. But I can confirm the crash. Reproduce: - open any document - open the spell-check dialog - press the Add button (although the "Mispelled word" field is empty) bluefish crashes immediately
Created attachment 77099 [details] full gdb backtrace attached is the full backtrace (long)
Fixed in CVS. Changed the "Add" button to "Add Word" to make its use more clear. The Add button is also disabled now when its usage is inappropriate. A new, more user friendly spell check dialog is on my TODO list.
*** Bug 396480 has been marked as a duplicate of this bug. ***
*** Bug 444992 has been marked as a duplicate of this bug. ***