Hi Michael and Misja, I'm having similar problems. Michael, could you try with an empty database (move ~/.gnubg/gnubg.db out of the way) and see if you can add a match/show the records. I'll try to find time to look at it in the weekend if you cannot reproduce.
Christian. On Thu, Aug 13, 2009 at 11:40 PM, Michael Petch<[email protected]> wrote: > > > On 13/08/09 2:38 PM, "Misja Alma" <[email protected]> wrote: > >> Sure, here it is: >> >> [Thread 0x7f8266c5f950 (LWP 20487) exited] >> >> Program received signal SIGSEGV, Segmentation fault. >> [Switching to Thread 0x7f8281b77820 (LWP 20481)] >> 0x00007f8281405197 in ?? () from /usr/lib/libsqlite3.so.0 >> (gdb) bt >> #0 0x00007f8281405197 in ?? () from /usr/lib/libsqlite3.so.0 >> #1 0x00007f82814057b8 in sqlite3_free () from /usr/lib/libsqlite3.so.0 >> #2 0x00007f8281410c46 in ?? () from /usr/lib/libsqlite3.so.0 >> #3 0x00007f828141085c in ?? () from /usr/lib/libsqlite3.so.0 >> #4 0x00007f8281411341 in ?? () from /usr/lib/libsqlite3.so.0 >> #5 0x00007f8281412e20 in ?? () from /usr/lib/libsqlite3.so.0 >> #6 0x00007f828143877c in sqlite3_close () from /usr/lib/libsqlite3.so.0 >> #7 0x0000000000438a50 in SQLiteDisconnect () at dbprovider.c:580 > > Interesting, reviewing the code it appears it wrote the match and then > crashed trying to close the database. Looking at the code I don't see an > obvious bug. > > So I can help hunt this down can you give me output of these commands: > > cat /proc/info > uname -a > > Thanks > > > > > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg > _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
