GnuCash + logging

[Tarlika Elisabeth Schmitz]

On Tue, 09 Oct 2007 18:04:11 -0400
Josh Sled <jsled at asynchronous.org> wrote:

> (Please remember to CC: the mailing list on all replies; using your
> mailer's "Reply to List" or "Reply to All" features are helpful.)

I know but do I need to include the embarrassing dummy questions?

> <#secure method=pgpmime mode=sign>
> Tarlika Elisabeth Schmitz <gnucash at numerixtechnology.de> writes:
> > On Mon, 08 Oct 2007 18:53:05 -0400
> > Josh Sled <jsled at asynchronous.org> wrote:
> >> If you're inclined, it would be good to provoke the crash in gdb,
> >> if only to get the stack trace at the point of that crash; that
> >> itself might be illustrative, but I doubt it will alone be useful.
> >
> >
> >
> > I had a reproducable crash to-day:
> > duplicate, crash, restart, duplicate same record, crash, restart,
> > save, duplicate same record, no crash
> >
> > Tried to run GnuCash in gdb but:
> >
> > "This GDB was configured as "i486-linux-gnu"..."/usr/bin/gnucash":
> > not in executable format: File format not recognized"
> >
> > /usr/bin/gnucash exists and is executable. 
> 
> To run gnucash within gdb, take a look at the HACKING file; if it's
> not installed by your distribution, try
> <http://svn.gnucash.org/repo/gnucash/trunk/HACKING>.
> 
> In short, invoke gdb as such:
> 
>     $ /usr/bin/gnucash-env gdb /usr/bin/gnucash-bin
>     [gdb version, &c.]
>     (gdb) run
>     [gdb/gnucash output...]
>     [... provoke crash...]
>     [... gdb crash-intercept output]
>     (gdb) backtrace
>     [useful stack info, hopefully]



I have been running gnucash in gdb everyday since, and it's up from 7am
till midnight (sad or what?). It just won't crash now. Bloody typical.

There are only 2 differences:
1) I run it in gdb
2) I save frequently



--


Best Regards,

Tarlika Elisabeth Schmitz


A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?