2.4.3 - not ready

Phil Longstaff plongstaff at rogers.com
Fri Feb 25 11:40:20 EST 2011

OK.  I'll release this weekend.

I used to be a hypochondriac AND a kleptomaniac. So I took something for it.

From: Christian Stimming <stimming at tuhh.de>
To: Phil Longstaff <plongstaff at rogers.com>
Cc: Gnucash Devel Mailing List <gnucash-devel at gnucash.org>
Sent: Fri, February 25, 2011 2:24:32 AM
Subject: Re: 2.4.3 - not ready

Dear Phil,

thanks for the release checking work.

However, I do not agree with your conclusion here. Your newly discovered bug 
hasn't been reported before, so it can't be very severe (even though it appeared 
to be a crasher in your test). On the other hand, we already discussed and 
agreed that 2.4.2 contains serious bugs that have been fixed already (mysql 
crash on windows, erroneous duplicate invoice feature) and those fixes alone 
already justify an imminent 2.4.3 release.

Hence, in this particular case I would have strongly preferred to have a 2.4.3 
release ASAP, even though other bugs like the one you discovered is still 
existing. But the fixes for the other severe bugs will mean that 2.4.3 will 
already be a big improvement over 2.4.2. We can subsequently fix other bugs like 
the one you've seen here, and include fixes for those in subsequent releases.

Thank you very much!



Zitat von Phil Longstaff <plongstaff at rogers.com>:
> I tagged and built 2.4.3.  It passes make check and make distcheck.
> However, when I run it, I get a segv when I close gnucash.  The problem
> seems to be during the call to gnc_dbi_unlock().  While looking for the
> current process pid in the lock table, the sqlite3 error fn is called.
> According to valgrind, when setting the error code, this is an invalid
> write, past the end of valid memory.
> I think this should be tracked down and solved before 2.4.3. is
> released.

More information about the gnucash-devel mailing list