Re: [sqlite] Is this test failure serious: *malloc*.transient.42 failures (expected [1 1], got [0 {}])?

On Thu, May 28, 2009 at 04:38:50PM -0400, D. Richard Hipp wrote: > >> To debug, set a breakpoint on sqlite3Fault(). That routine is > >> called whenever an OOM fault is simulated. Run to the point of the > >> OOM fault that is causing the problem. Figure out which malloc() > >> is falling and

Re: [sqlite] Is this test failure serious: *malloc*.transient.42 failures (expected [1 1], got [0 {}])?

On May 28, 2009, at 4:12 PM, Nicolas Williams wrote: > >> To debug, set a breakpoint on sqlite3Fault(). That routine is called >> whenever an OOM fault is simulated. Run to the point of the OOM >> fault >> that is causing the problem. Figure out which malloc() is falling >> and >> why the

Re: [sqlite] Is this test failure serious: *malloc*.transient.42 failures (expected [1 1], got [0 {}])?

On Thu, May 28, 2009 at 04:00:07PM -0400, D. Richard Hipp wrote: > These are tests that simulate a malloc() failure (aka "out-of-memory" > or OOM fault) to verify that nothing crashes or leaks following an OOM > fault and that an SQLITE_NOMEM error is reported back out at the top > level.

Re: [sqlite] Is this test failure serious: *malloc*.transient.42 failures (expected [1 1], got [0 {}])?

On May 28, 2009, at 3:32 PM, Nicolas Williams wrote: > I'm getting these failures in gmake fulltest output for SQLite3 > 3.6.14.2 > on Solaris x86 (32- and 64-bit): > > altermalloc-1.transient.42... > Expected: [1 1] > Got: [0 {}] > > Are these failures a problem? How would I start to

[sqlite] Is this test failure serious: *malloc*.transient.42 failures (expected [1 1], got [0 {}])?

I'm getting these failures in gmake fulltest output for SQLite3 3.6.14.2 on Solaris x86 (32- and 64-bit): altermalloc-1.transient.42... Expected: [1 1] Got: [0 {}] ... attachmalloc-1.transient.42... Expected: [1 1] Got: [0 {}] ... malloc6-1.transient.42... Expected: [1 1] Got: [0