🚀 go-pugleaf

Never seen something like this, but you can try to step through the
execution of your application source code. ('View'+'Project Source'). Set a
breakpoint at the first line. (Which should be something like
Application.initialize;) Let us know if the Access Violation occures even
before this one.

Could hopefully be to some help...

-- 
Edgar Vorland

{Remove  '~' from mail adress. This is to avoid
spawn. Sorry! }
e~vorland@readmatre.no

Nick Reseigh <nickr@solcov.demon.co.uk> wrote in article
<344320d0.77675351@news.demon.co.uk>...
> Is there anyone out there who has had a similar occurrence?
> 
> I'm running delphi developer 2, and this appears to happen way before the
first
> line of my application is executed.  From the link map, this address is
way
> outside my program, so maybe something took a wild branch into the
> stratosphere?   I reinstalled delphi, but the problem (unfortunately)
persists.
> 
> Any help/ideas gratefully received................./Nick
> 

> I'm running delphi developer 2, and this appears to happen way before the
first
> line of my application is executed.  From the link map, this address is
way
> outside my program, so maybe something took a wild branch into the
> stratosphere?   I reinstalled delphi, but the problem (unfortunately)
persists.

This normally happens with 3rd party or custom components that do not
initialise the properties correctly or have faulty logic in events that are
accessing properties or structures that rely on some other event being
called first. One that comes to mind is the "OnChange" event which gets
called as the component is displayed even though "logically thinking"
suggests it should not as nothing as has changed yet. It is not easy to
find the offending component. Try to remember when the problem first
occured and what non-Borland components you were working with at the time
and systematically remove and replace them until you find the offending
component. If it your own component or you have the source you will be able
to step thru in debug and find the faulty logic and correct it.

Good Hunting
Mike Heydon

 read of FFFFFFFF means that something (Delphi App), couldn't create
something...  (basically, it's a False)

--
Jason Wallace
SL Software
DarkElf@SLSoftware.reno.nv.us
--
"We are MicroSoft.  You will be assimilated.  Resistance is Futile."
--
Nick Reseigh wrote in message <344320d0.77675351@news.demon.co.uk>...
>Is there anyone out there who has had a similar occurrence?
>
>I'm running delphi developer 2, and this appears to happen way before the
first
>line of my application is executed.  From the link map, this address is way
>outside my program, so maybe something took a wild branch into the
>stratosphere?   I reinstalled delphi, but the problem (unfortunately)
persists.
>
>Any help/ideas gratefully received................./Nick

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?

If everything fails, you will have to rewrite your application,
noticing when the problem pops up.

Ari.


Nick Reseigh wrote:

> Is there anyone out there who has had a similar occurrence?
>
> I'm running delphi developer 2, and this appears to happen way before
> the first
> line of my application is executed.  From the link map, this address
> is way
> outside my program, so maybe something took a wild branch into the
> stratosphere?   I reinstalled delphi, but the problem (unfortunately)
> persists.
>
> Any help/ideas gratefully received................./Nick

> 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. *
******************************************************

In article <01bcda9a$89781ba0$0101a8c0@lemming> "=?ISO-8859-1?Q?Ars=E8ne_von_Wyss_=5BAntispam_-_email_address_in_messag?= writes:

>* 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


You should certainly post how to do it, for all the world to read.

This is a multi-part message in MIME format.

------=_NextPart_000_01BCDE2B.658C8840
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

> >* 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)

> You should certainly post how to do it, for all the world to read.

The registry file to enable it is attached to this message. It will enable
the CPU window in both Delphi 2 and 3. Note that you have to close and
reopen Delphi after installing the reg file if Delphi was running. You will
have a new "CPU" option in the "Windows" menu.

In Delphi 2, the CPU window is quite simple; it only displays a disassembly
of the actual source position and allows you to do single CPU-instruction
steps. You can use the inspect window to look at the content of registers
(EAX,ECX,EDX,...).

The Delphi 3 CPU window is quite powerful, providing a similar CPU window
like Turbo Debugger does, with all registers and data windows.

The only thing I don't understand is why Borland made such a secret out of
it...

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. *
******************************************************

------=_NextPart_000_01BCDE2B.658C8840
Content-Type: application/octet-stream; name="EnableCPU.reg"
Content-Transfer-Encoding: 7bit
Content-Description: EnableCPU.reg (Registrierungsdatei)
Content-Disposition: attachment; filename="EnableCPU.reg"

REGEDIT4

[HKEY_CURRENT_USER\Software\Borland\Delphi\2.0\Debugging]
"EnableCPU"="1"

[HKEY_CURRENT_USER\Software\Borland\Delphi\3.0\Debugging]
"EnableCPU"="1"

------=_NextPart_000_01BCDE2B.658C8840--

This is a multi-part message in MIME format.
--------------335E094D3CF9682838BAC716
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



Sundial Services wrote:

> In article <01bcda9a$89781ba0$0101a8c0@lemming> "=?ISO-8859-1?Q?Ars=E8ne_von_Wyss_=5BAntispam_-_email_address_in_messag?= writes:
>
> >* 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
>
> You should certainly post how to do it, for all the world to read.

  Just merge this file to the registry. That should do the trick!
Start up Delphi and goto View | Cpu
HocusPocus
Atli

--------------335E094D3CF9682838BAC716
Content-Type: application/x-unknown-content-type-regfile; name="dis.reg"
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="dis.reg"

UkVHRURJVDQNCg0KW0hLRVlfQ1VSUkVOVF9VU0VSXFNvZnR3YXJlXEJvcmxhbmRcRGVscGhp
XDIuMFxEZWJ1Z2dpbmddDQoiRW5hYmxlQ3B1Ij0iMSINCg0K
--------------335E094D3CF9682838BAC716--

On 21 Oct 97 13:28:58 GMT, "Ars�ne von Wyss [Antispam - email address
in message]" <avonwyss@beaulieu-software.nospam.ch> wrote:

>The only thing I don't understand is why Borland made such a secret out of
>it...

Because it's incomplete.

-Steve