Am 15.04.2006 um 00:50 schrieb Thomas Chust:
On Fri, 14 Apr 2006, Will Leshner wrote:
On 4/14/06, Thomas Chust <[EMAIL PROTECTED]> wrote:
I just downloaded the 3.3.5 distribution tarball and confirmed
that the
problem occurs with a binary built from that codebase as well.
I assume you guys are refering to the tip, right. If I download the
"stable" 3.3.5 distribution and build that on 10.4.6, it runs and
exits just fine.
Hello,
I referred to the usual stable release tarball found on the SQLite3
webpage.
But I just figured out that the problem apparently had not much to
do with SQLite3 itself. A debugger session showed that the segfault
occurred in the command history library at the point where the
history was saved. I found nothing unusual about my history file,
but after deleting it everything was back to normal.
I get this crash from time to time and also found that (1) the crash
happens in the system library handling history and (2) deleting the
history file gets me back to normal.
I believe (not 100% sure, though) it's related to long command lines
in sqlite: if one of the command lines that are being stashed into
the history file gets too long, the history code will freak out when
trying to save the file. Might be a buffer overrun in the history
code...
</jum>
