I traced this error down a bit, it only appears when using windows'
PostMessage() to communicate between applications. Both applications have
their own database handles for sure. When one app gets some data, it simply
uses PostMessage() to inform the other app that some data has been received.
It is at this point that if I try accessing the database in this message
handler, the memory leak occurrs. I even took the additional precaution of
creating an entirely new database handle inside the message handler itself.
If I replace PostMessage() with SendMessage(), no leak occurrs. However,
replacing PostMessage() with SendMessage() would be a huge penalty. Any
ideas why there is a problem here?
Thanks,
Mark
On 9/15/05, Reid Thompson <[EMAIL PROTECTED]> wrote:
>
> Jay Sprenkle wrote:
> > The premier analysis tool that I know about is valgrind:
> >
> http://valgrind.org/info/about.html
>
> splint may be of interest also http://www.splint.org/
>
> reid
>
