> 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.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
