GnuCash + logging

[Tarlika Elisabeth Schmitz]

On Mon, 08 Oct 2007 18:53:05 -0400
Josh Sled <jsled at asynchronous.org> wrote:

> (I fixed the misspelling in the Subject :p)

I thought it was quite funny, that is after I had cooled down. ;-)

> 
> Tarlika Elisabeth Schmitz <gnucash at numerixtechnology.de> writes:

> The key thing for bug fixing is reproducibility.  If you can identify
> a 100%-reproducible sequence of steps to trigger the crash, it's far
> more likely to be a fixable problem.  It sounds like normal usage
> will provoke the crash frequently enough to be useful however...

On a previous occasion I think I particular record always caused a
crash. I shall monitor this and retry duplicate on same record next
time.

> If you're willing to make your datafile public, we could see if
> someone can reproduce the crash.  It's understandable that you'd not
> want to make it public.  Perhaps you can privately send it to me, and

The thought had occurred to me, too. Not a good idea I think.

> Even better would be to have 100%-reliable reproduction instructions
> from a new/empty datafile.  You might want to create a new or test
> datafile, just to see if the problem is reproducible there.

I'll try that once I have a better idea why and when this is happening.

> 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.

Will do. I've got the thing open all day. It's guaranteed to happen
during a session.

TES

--


Best Regards,

Tarlika Elisabeth Schmitz


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