[GNC] gnucash-user Digest, Vol 233, Issue 83

[Kalpesh Patel]

This might be the bug that I had hit in 4.8 of GNC which might had been
carried forward since 3.11 and prior when performing "Check & Repair" (yah,
I was a Quicken User). When I ran into the bug, crash was with "Check &
Repairs All" which likely uses same routines under the hood. Bug 798346 is
the ID for it which was fixed by John.


Best bet is to go in "blindly" and not perform "Check & Repair" until you
are past version 4.8 of GNC.



----------------------------------------------------------------------

Message: 1
Date: Sun, 28 Aug 2022 15:10:13 +0200
From: "rsbrux" <	>
To: <gnucash-user at gnucash.org>
Subject: Re: [GNC] GC 3.11 crashes during "Check & Repair"
Message-ID:
	
<!&!AAAAAAAAAAAuAAAAAAAAAExfBJ/fSBxAqM7oRtz1TdsBAMO2jhD3dRHOtM0AqgC7tuYAAAAA
AA4AABAAAAChLMzAAN32SKHihsh5lcnzAQAAAAA=@yahoo.com>
	
Content-Type: text/plain;	charset="utf-8"

Thanks for all the references, particularly for reminding me to check the
trace file.  Unfortunately, the only error messages logged in the trace file
were at the beginning of the process:
* 09:31:56 ERROR <gnc.app-utils> gnc_process_get_fd: assertion 'proc' failed
* 09:31:56 ERROR <gnc.app-utils> gnc_detach_process: assertion 'proc &&
proc->pid' failed
I am reluctant to venture into gdb, much less compiling GC myself, but
perhaps these lines at the end of the trace file give a hint to which part
of the XML file is giving "Check & Repair" indigestion:
* 10:07:41  INFO <gnc.engine.scrub> [xaccAccountScrubImbalance] Finished
processing split 113 of 304
* 10:07:41  INFO <gnc.engine.scrub> [xaccAccountScrubImbalance] Start
processing split 114 of 304
Is there any way for me to identify what part of the XML file "split 114 of
304" corresponds to?
Given that GC was started several times by mistake when price update were
running on the same file, I suspect that the bad records are in the price
history part of the DB.
I can readily do without the price history if there is some way of migrating
all of the transactions to the new file version.

Of course I ran 3.11 on a copy.

------------------------------