Crash When Entering Tax Data - GC 2.4.4 (Debian Squeeze Backports)
John Ralls
jralls at ceridwen.us
Tue Feb 28 16:11:53 EST 2012
On Feb 28, 2012, at 10:32 AM, Digger wrote:
> Hi John,
>
> Thanks for your interest!
>
> Well, this is your lucky day! I'm fairly new to Linux and don't have much
> experience chasing bugs (at least since my FORTRAN and MS-DOS days).
>
> I googled bug 611474, but could not get anything that I could understand.
>
> As per your instructions, I replicated the problem. Here are the entire
> contents of the resultant "/tmp/gnucash.trace file:
>
> ---------------------------------------
>
> * 11:20:06 CRIT <Gtk> gtk_entry_set_text: assertion `text != NULL' failed
>
> ---------------------------------------
>
>
> John, I realize you are looking for more information and I am eager to
> comply....I'm just a bit uneducated concerning these matter is all. In
> order to up the verbosity in the above-mentioned gnucash.trace file, do I
> need to load the debian "gdb" package and go to school on it? (Once again,
> I'm using Debian Squeeze atm.)
>
> Thanks for your help!
Hmm. If that's it, then it's not coming from Scheme, so it's a different bug.
You could get a stack trace with gdb, the instructions are at
http://wiki.gnucash.org/wiki/FAQ#Q:_How_do_I_run_GnuCash_under_gdb_and_get_a_stack_trace.3F
I suspect, though, that Debian have stripped the symbols and the trace won't be that helpful. It's worth a try anyway.
There might be some more information if you run from the command line (I'm guessing that you're launching Gnucash from the menu):
Open a terminal and at the prompt type
gnucash --debug
There may be some output that debian is eating, and the --debug argument will put some more context information into gnucash.trace.
Regards,
John Ralls
More information about the gnucash-user
mailing list