Help with debug

[Phil Lodwick]

Hi,

I have been debugging a problem today and am running low on batteries.  I am
hoping somebody can look at the attached snippet of log and point me in the
right direction.
> From what I can tell, there is a DLL called snoopy.dll that does a whole

bunch of allocs and reallocs and then tries to reference a NULL pointer which
causes an unhandled exception.  The code goes through a loop and does not
always crash on the same iteration, but it always seems to crash at the same
address.

This code does not crash on Windows.  Just getting lucky?

Unfortunately I do not have the sources to this code, so it makes life a
little more difficult.

Any good ideas for my next step in debugging?

Thanks,
Phil

[Damjan Jovanovic]

On 3/15/07, Phil Lodwick  wrote:
> Hi,
>
> I have been debugging a problem today and am running low on batteries.  I am
> hoping somebody can look at the attached snippet of log and point me in the
> right direction.
> > From what I can tell, there is a DLL called snoopy.dll that does a whole
>
> bunch of allocs and reallocs and then tries to reference a NULL pointer which
> causes an unhandled exception.  The code goes through a loop and does not
> always crash on the same iteration, but it always seems to crash at the same
> address.
>
> This code does not crash on Windows.  Just getting lucky?
>
> Unfortunately I do not have the sources to this code, so it makes life a
> little more difficult.
>
> Any good ideas for my next step in debugging?

Try do a +all trace and see what the thread was doing just before the crash.

Failing that, you'll have to run it winedbg and disassemble around the
crashed instruction and try decipher what it's doing.
> Thanks,
> Phil

Good luck
Damjan