RE: [Devel] NT crash in psaux

[Blinn, Eric W]

Hi Werner,

I had built fully optimized and also debug without optimization, but not
otherwise played around with optimization levels.  It crashed either way due
to the dangling pointer, so I'm not inclined to think experimenting with the
intermediate optimization levels will buy me anything.  

Now that I can at least reproduce it consistently, I'll make time eventually
to go back and debug the underlying issue that I suspect is still there.
For now though, I'm satisfied with my current solution and I need to get
back to tying up other loose ends and getting this release of our
application out the door.  Appreciate all the help.

Thanks,
Eric

> -----Original Message-----
> From: Werner LEMBERG [mailto:address@hidden
> Sent: Tuesday, February 06, 2001 8:01 AM
> To: address@hidden
> Cc: address@hidden
> Subject: Re: [Devel] NT crash in psaux
> 
> 
> 
> > Anyway, I've got a local fix that does fix *my* bug.  I think it
> > fulfills the intent of the code while protecting against a free
> > memory read from the dangling pointer.  However, I'm not so sure
> > that isn't just masking an underlying problem.  The bigger question
> > is why object and table->block are sometimes pointing at the same
> > block of memory and whether that is a valid state.
> 
> Have you experimented with compiler optimization flags?
> 
> 
>     Werner
>