🚀 go-pugleaf

> Address 0xffffffff is Nil, so there is some pointer pointing to
> nothing, and being used. This may occur even before YOUR
> code is running, for example in initialization of components
> or pre compiled units. Are you using standard component library?
> are you using non-standard components? units? other extras?

Address 0xffffffff is not NIL (at least not in Turbo Pascal, Delphi 1,
Delphi 2, Delphi 3, Assembly...) but -1 (for a 32-Bit value).

NIL is 0. However, you often get the access violation above when trying to
access an object that has a nil pointer. It seems to me like the first four
bytes of memory at Address 0 are 0xFFFFFFFF, which is interpreted as the
VMT (Virtual Methods Table) pointer of the (uninitialized) object (but I
did not try it).

> > Any help/ideas gratefully received................./Nick

* You may use Assigned(Object) to ckeck is a pointer is NIL or not.
* Trace the program step-by-step until you get the error to find the
location if the debugger is unable to resolve the address.
* If your project is a VCL project, you can enable the console window
{$CONSOLE in the Application widow) and use it as debug output; just use
 WriteLn('Debug string!');
to write text in this window.
* You can enable the hidden Disassembler/Debugger of Delphi, which will
probably show you the exact address and assembly code that caused the
exception (write me a mail if you don't know how to enable it)

Hope this helps...

Ars�ne von Wyss
avonwyss @ beaulieu-software.ch

******************************************************
*    I removed my reply address to avoid spamming.   *
* Please use the address above to reply or write me. *
******************************************************