Re: [sqlite] segmentation violation in fulltest on Mac OS X

Am 19.01.2009 um 18:42 schrieb D. Richard Hipp: > > On Jan 19, 2009, at 3:50 AM, Jens Miltner wrote: > >> Hello, >> >> I just upgraded to sqlite 3.6.10 and keep getting a segmentation >> violation when running the full tests on Mac OS X: >> The last test completed is consistently thread001.1.3.

Re: [sqlite] segmentation violation in fulltest on Mac OS X

> Of course, I wasted 4 hours tracking the problem down. This is > yet another episode that demonstrates how threads are a pernicious > evil that should be studiously avoided in any program that you > actually want to work. Threads cause hard-to-trace bugs. Threads > result in

Re: [sqlite] segmentation violation in fulltest on Mac OS X

Hello, Threads: use them, but don't abuse them Threads don't kill programs, programmers do ;-) Martin D. Richard Hipp wrote: > On Jan 19, 2009, at 3:50 AM, Jens Miltner wrote: > > >> Hello, >> >> I just upgraded to sqlite 3.6.10 and keep getting a segmentation >> violation when running the

Re: [sqlite] segmentation violation in fulltest on Mac OS X

"D. Richard Hipp" said, > slower. Just say "No" to threads... Can I quote you on that? :-) josé ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] segmentation violation in fulltest on Mac OS X

On Jan 19, 2009, at 3:50 AM, Jens Miltner wrote: > Hello, > > I just upgraded to sqlite 3.6.10 and keep getting a segmentation > violation when running the full tests on Mac OS X: > The last test completed is consistently thread001.1.3. > This was a problem in the testing logic, not in the

[sqlite] segmentation violation in fulltest on Mac OS X

Hello, I just upgraded to sqlite 3.6.10 and keep getting a segmentation violation when running the full tests on Mac OS X: The last test completed is consistently thread001.1.3. We're using a custom Xcode build of sqlite, so there's a chance that it has to do with our build settings.