Actually, this one may be as simple as using va_list ap_copy in StringBuffer to ensure that the argument list is valid and guard against an off-by-one bug. I have checked in a new version to the repository and if you could test, that would be swell. Otherwise if you get this again, could you look closer at the StringBuffer memory buffer to see if it looks valid.
On 5. april. 2008, at 16.59, Paul J Stevens wrote:
(gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb78cbf75 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb78cd8f1 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7d01b95 in Util_abort (e=0xb7d102a0 "MemoryException -- %s at %s in line %d\n") at src/util/Util.c:83 #4 0xb7d023d2 in Mem_resize (p=0x5316e008, size=1665138688, file=0xb7d214c0 "src/util/StringBuffer.c", line=61) at src/util/ Mem.c:76 #5 0xb7d07c29 in StringBuffer_vappend (S=0x8115438, s=0x81008c0 "UPDATE OR IGNORE dbmail_mailboxes SET mtime=STRFTIME('%Y-%m-%d %H:%M:%S','now','localtime') WHERE mailbox_idnr=2", ap=0xbfe38778 "{z\t\b��\t\b�") at src/util/StringBuffer.c:61 #6 0xb7d0e88f in SQLiteConnection_execute (C=0x8115de8, sql=0x81008c0 "UPDATE OR IGNORE dbmail_mailboxes SET mtime=STRFTIME('%Y-%m-%d %H:%M:%S','now','localtime') WHERE mailbox_idnr=2", ap=0xbfe38778 "{z\t\b��\t\b�") at src/db/sqlite/ SQLiteConnection.c:174