GNOME Bugzilla – Bug 514264
crash navigating register with keyboard
Last modified: 2018-06-29 22:00:42 UTC
What were you doing when the application crashed? editing a split, using the down arrow to fix next line Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106209280 vsize: 106209280 resident: 45375488 share: 17440768 rss: 45375488 rss_rlim: 4294967295 CPU usage: start_time: 1202120886 rtime: 1528 utime: 1479 stime: 49 cutime:31 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnucash' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208506656 (LWP 2508)] [New Thread -1253184624 (LWP 2522)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188030
Thread 1 (Thread -1208506656 (LWP 2508))
----------- .xsession-errors (6 sec old) --------------------- WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: cast to 'QString' error X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2e0003a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3940a23 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x391d10a "/usr/bin/gnucash": not in executable format: File format not recognized --------------------------------------------------
*** Bug 514267 has been marked as a duplicate of this bug. ***
*** Bug 516167 has been marked as a duplicate of this bug. ***
The variable "info" in gnc_split_register_load() in split-register-load.c does not get checked to see if it might be NULL before being dereferenced. That's a problem, but I don't think that's what is causing this gdb output. It looks more like the assert() at line 277 of the same function. I've never touched the register code, so I'm surely the wrong person to take this on, but I thought this information would be useful to whoever does.
*** This bug has been marked as a duplicate of 501526 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=514264. Please update any external references or bookmarks.