Re: Form.Create() crashes...
- From: sap <sap@xxxxxxxxxxx>
- Date: Sat, 01 Mar 2008 15:07:53 +0200
Anton wrote:
Line 2569 of the vcl\Forms.pas unit:
GlobalNameSpace.EndWrite;
You only said you have 'Windows GUI-rich application'.
So I have no simple tricks to offer, just hard work: So roughly rip off
so much functionality and code from that Form in the DLL, so that it
starts to load and work again.
I have to use this technique every now and then when some mysterious and
hard to find errors appear. Mostly they are some automated Control
events that insidiously fire in the background, somewhere outside the
point that I carefully try to debug.
I can easily freeze my project anytime to a ZIP file. And in seconds
restore any previous project stage back again from any of those ZIP
files. It's relatively painless and quick to roughly locate the area of
the error. First crudely rip off something like 50% or the original
controls and code, and check if the error lied in that chunk, etc.
If you are not able to succesfully call even the simplest, bare Form
from your DLL then you are doing something very much wrong. Then you'll
have to Google for some simple working example about DLLs from the net.
Once you have a working Form and DLL, then gradually put back all the
functionality and code. You will inevitably find the point(s) where the
problem actually was.
.
- Follow-Ups:
- Re: Form.Create() crashes...
- From: Anton
- Re: Form.Create() crashes...
- Prev by Date: Re: Preventing Delphi debugging into VCL
- Next by Date: Intercept print jobs
- Previous by thread: Re: Preventing Delphi debugging into VCL
- Next by thread: Re: Form.Create() crashes...
- Index(es):