--- Dan Kennedy <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-08-30 at 10:13 -0700, Joe Wilson wrote:
> > Compiled without -DSQLITE_DEBUG=1 which presumably changes the timing.
> >
> > cvs up -A
> > make distclean
> > # thrd35.c = http://marc.info/?l=sqlite-users&m=118848741522192&w=2
> > cp thrd35.c src/shell.c
> > ./configure --disable-shared && make LIBPTHREAD=-lpthread sqlite3
> > ./sqlite3
> > valgrind -v ./sqlite3 2>&1 | tee v.log
>
> Try adding --enable-threadsafe to the configure command. Does the
> valgrind log look any better after doing so?
That explains it. I'm surprised I missed that.
I thought there was a checkin a few months ago that made sqlite3
threadsafe by default.
os_unix.c
revision 1.128
date: 2007/04/01 18:46:19; author: drh; state: Exp; lines: +4 -1
Make unix builds threadsafe by default.
I guess this is no longer the case?
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
