G2 crash/Split info

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

G2 crash/Split info

Phil Longstaff-2
I'm currently running SuSE 9.3 and have g2 built from source.  I have a very
reproducible crash which I'm trying to find the cause of (there are a number
of Bugzilla bugs which this is a duplicate of - 108347
http://bugzilla.gnome.org/show_bug.cgi?id=108347, 141287 (dup of 108347)).  
The crash is in XaccTransGetDate() with a transaction address of 0x01 (or
other small non-zero values).  Note that by doing the same procedure, I've
also seen the stack in 125480
(http://bugzilla.gnome.org/show_bug.cgi?id=125480).

To reproduce, create a new file with a bank account and income account (I
don't know if the types matter).  Open bank account and create about 20
deposit transactions (I just created one, copied it, and pasted to get about
20 transactions).  Set to transaction journal display.  Set the cursor on the
first transaction.  Quickly press Tab-backspace-tab-backspace-... to remove
all of the contents of the splits.

I set a breakpoint (using kdbg) in gnc_split_register_load() in the for loop
which loops through the splits.  The breakpoint is hit when the register is
first being loaded, before I start the tab-bs-tab-bs...  The splits seem to
show garbage, yet the register displays correctly.  Everything was compiled
with -g -O0.  Is this a known issue with splits?

My guess is that there needs to be better interlocking between updating splits
and displaying them.

Phil
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: G2 crash/Split info

Phil Longstaff-2
Small update:

On February 11, 2006 01:05 pm, Phil Longstaff wrote:

> I'm currently running SuSE 9.3 and have g2 built from source.  I have a
> very reproducible crash which I'm trying to find the cause of (there are a
> number of Bugzilla bugs which this is a duplicate of - 108347
> http://bugzilla.gnome.org/show_bug.cgi?id=108347, 141287 (dup of 108347)).
> The crash is in XaccTransGetDate() with a transaction address of 0x01 (or
> other small non-zero values).  Note that by doing the same procedure, I've
> also seen the stack in 125480
> (http://bugzilla.gnome.org/show_bug.cgi?id=125480).
>
> To reproduce, create a new file with a bank account and income account (I
> don't know if the types matter).  Open bank account and create about 20
> deposit transactions (I just created one, copied it, and pasted to get
> about 20 transactions).  Set to transaction journal display.  Set the
> cursor on the first transaction.  Quickly press
> Tab-backspace-tab-backspace-... to remove all of the contents of the
> splits.

I tried again slowly deleting all the splits.  It still crashed.

>
> I set a breakpoint (using kdbg) in gnc_split_register_load() in the for
> loop which loops through the splits.  The breakpoint is hit when the
> register is first being loaded, before I start the tab-bs-tab-bs...  The
> splits seem to show garbage, yet the register displays correctly.
> Everything was compiled with -g -O0.  Is this a known issue with splits?

I tried again with gdb.  Same garbage.

>
> My guess is that there needs to be better interlocking between updating
> splits and displaying them.
>
> Phil
> _______________________________________________
> gnucash-devel mailing list
> [hidden email]
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: G2 crash/Split info

Derek Atkins
Phil Longstaff <[hidden email]> writes:

>> I set a breakpoint (using kdbg) in gnc_split_register_load() in the for
>> loop which loops through the splits.  The breakpoint is hit when the
>> register is first being loaded, before I start the tab-bs-tab-bs...  The
>> splits seem to show garbage, yet the register displays correctly.
>> Everything was compiled with -g -O0.  Is this a known issue with splits?
>
> I tried again with gdb.  Same garbage.

For what it's worth, I've also seen gdb garbage while trying to
debug some problems.  I really suspect there's a stack-scribble
or some other memory-corruption bug going on, but those kinds of
things are really hard to track down.

-derek
--
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [hidden email]                        PGP key available
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel