Quoting Aaron Scott-Boddendijk <[EMAIL PROTECTED]>:
> > Is someone in a position to know about the type of message that Delphi
> > generates when you deference a nil pointer.
> >
> > It used to be that you knew because the address given was FFFFFFFF. But
> these
> > days the address seems to be much closer to 0.
>
> It's more than just nil pointers that'll give the EAccessViolation... Any
> uninitialised
> pointer (including used pointers which have had their memory released)
> which
> steps over the legal memory boundary... The exception message should read
> EAccessViolation and that's enough to identify an dangling pointer
> dereference.
I think all of you who replied mised the point. We all know that lots of things
can cause access violations. I get one regularly in D3 when I install new
components. But there is a distinction between one in my code that I have
written and one from some other part of the system. And it used to be that you
could tell easily the difference, now you can't.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
