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 ./testf
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]>
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 me
Shawn Walker <[EMAIL PROTECTED]> wrote:
> Has anybody run Bounds Checker on SQLite 3?
valgrind (http://valgrind.org/) shows that SQLite3 is free
of memory leaks and buffer overruns.
--
D. Richard Hipp <[EMAIL PROTECTED]>
Has anybody run Bounds Checker on SQLite 3? I'm getting a lot of memory
leaks, overruns, etc that is being reported by Bounds Checker. But, what is
strange is that the warning message doesn't match up with the source for
some reason. For example:
Memory Leak Leaving Scope: Variable z refere
5 matches
Mail list logo