Re: [sqlite] Bounds Checker

Thanks! I will run that test on Monday and let you know what BoundsChecker finds. Thanks, Shawn [EMAIL PROTECTED] wrote: Shawn Walker <[EMAIL PROTECTED]> wrote: What regression testing did you use? I would like to run the same test with Bounds Checker and see what I see. valgrind

Re: [sqlite] Bounds Checker

Shawn Walker <[EMAIL PROTECTED]> wrote: > What regression testing did you use? I would like to run the same test > with Bounds Checker and see what I see. > valgrind ./testfixture ../sqlite/test/quick.test -- D. Richard Hipp <[EMAIL PROTECTED]>

[sqlite] problem with sqlite3_exec method

Hello, I'm sorry but even after looking in the archives I haven't found any help on this subject : I'm testing a very simple C program that uses SQLite. The sqlite3_open method works fine and the database opens normaly, but then I get an error coming from the sqlite3_exec method :

Re: [sqlite] RE: UNICODE Support

Consider upgrading to 3.3.6. The following are some changes related to the UTF stuff. *2006 June 6 (3.3.6)* - Fix an obscure segfault in UTF-8 to UTF-16 conversions *2006 April 5 (3.3.5)* - The sqlite3_create_collation() function honors the SQLITE_UTF16_ALIGNED flag. On 8/4/06,

Re: [sqlite] Bounds Checker

What regression testing did you use? I would like to run the same test with Bounds Checker and see what I see. Shawn [EMAIL PROTECTED] wrote: Shawn Walker <[EMAIL PROTECTED]> wrote: Has anybody run Bounds Checker on SQLite 3? valgrind (http://valgrind.org/) shows that SQLite3 is free of

Re: [sqlite] sqlite 3.3.6 EXPLAIN QUERY PLAN segfaults under Linux FC5

Brian Dantes <[EMAIL PROTECTED]> wrote: > I get the following segv and stack trace in gdb every time I try > > sqlite> EXPLAIN QUERY PLAN ... > > where ... is any query you like. > > Program received signal SIGSEGV, Segmentation fault. > 0x00c33013 in strlen () from /lib/libc.so.6 > (gdb) where