problems with sql-backend

[Rolf Leggewie]

Hi,

I've been using the sql-backend for quite some time.  I've been
compiling my deb packages from svn to do that.  I recently upgraded my
machine from lucid to karmic and cooked up a new svn snapshot at about
the same time.  I believe I had previously been running r18249 for quite
a while without any trouble.

After the update to r18792, one of my sqlite3-based gnucash files
started acting up about a scheduled transaction which was due.  After
acknowleding it, I got a message "unable to save database".  The file
itself would not open.  Other gnucash databases were still fine.

I tried going back to 18249, but for unfathomable reasons it was quite
difficult to get it back to compile.  In the end, I had to disable
python-bindings because that just would not work.  I don't think this
will be an issue, though.  Unfortunately, I still can't open my problem
file in gnucash, because gnucash now chooses to crash.

terminal: http://paste.debian.net/64798/
gdb trace: http://paste.debian.net/64797/

I hope this helps you guys and me.

Phil, do you have any idea what's going on here?  Any suggestion how I
can get back to work?  The database itself seems to be fine.  I can see
the data without any problem in the sqlite CLI client or ooffice.

Regards

Rolf