GNOME Bugzilla – Bug 361057
Crash when splitting transaction
Last modified: 2018-06-29 21:13:32 UTC
Distribution: Debian testing/unstable Package: GnuCash Severity: major Version: GNOME2.14.2 1.9.8 Gnome-Distributor: Debian Synopsis: Crash when splitting transaction Bugzilla-Product: GnuCash Bugzilla-Component: Register Bugzilla-Version: 1.9.8 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: I created a new transaction in Liabilities:Credit Cards:My Credit Card and entered a payee of Staples. It appears that this payee had previously been memorized, but no account appeared when I tabbed. I entered Expenses:Home, an amount, and hit C-p to edit the splits. CRASH. I fired up gnucash again, and did the same thing. CRASH. I use both memorized transactions and C-p to edit splits a lot and this is the first crash I've seen in gnucash 1.9.8. Because there the account field was blank when I tabbed this memorized transaction and I don't think that I've seen that before, I suspect that the memorized transaction is somehow corrupted. If you can provide some direction for grabbing the relevant bits from the saved file, I can do so. Unfortunately, bug-buddy isn't letting me restart gnucash until this bug report is done, so I'll assume that life will be OK if I do NOT tab to complete this particular memorized transaction. Looks like 2.0.1 has percolated into Debian testing so I'll have that on my next upgrade. Does this sound familiar? Would it be fixed in 2.0? Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnucash' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231411520 (LWP 2003)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75545
Thread 1 (Thread -1231411520 (LWP 2003))
------- Bug created by bug-buddy at 2006-10-10 04:15 -------
bug#352115 and bug#344935 have very similar backtraces; identical from #17 gnc_table_move_cursor_gui() onwards. However, your backtrace just like the other two ones is not too informative; can you recompile gnucash with debugging enabled and see whether you get a more detailed stack trace (with line numbers and argument values of each function call)? Thanks a lot.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Sorry the stripped trace wasn't helpful, Christian. Is there more than one g_assert_warning() called gnc_split_register_load? If this problem comes up again, I'll try to recompile with -g. Since I use Debian pre-built packages, it's a bit of an effort to obtain and compile the source.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=361057. Please update any external references or bookmarks.