The
actual address of the exception should help - or where it is raised, cause if
you then find the line in error you can see what is happening/what is being
accessed.
If the
address belongs in the just freed DLL, then using the module window, note the
base address of the DLL (I normally allocate all my DLL's to different base
addresses to avoid DLL relocation on loading - it makes this process simpler).
When you load the DLL again, find what code is at this address, at least it will
show you the offending code (Will need all your debug options turned on eg stack
frames, debug dcus etc)
Myles
-----Original Message----- From: Phil Middlemiss [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 September 2001 2:43 p.m. To: Multiple recipients of list delphi Subject: Re: [DUG]: DLLs
|
- RE: [DUG]: DLLs Cooke, Andrew
- [DUG]: DLLs Aaron Scott-Boddendijk
- Re: [DUG]: DLLs Aaron Scott-Boddendijk
- RE: [DUG]: DLLs Cooke, Andrew
- Re: [DUG]: DLLs Aaron Scott-Boddendijk
- [DUG]: DLLs Robert Martin
- RE: [DUG]: DLLs Jim Zheng
- Re: [DUG]: DLLs Robert Martin
- Re: [DUG]: DLLs Phil Middlemiss
- Re: [DUG]: DLLs Robert Martin
- RE: [DUG]: DLLs Myles Penlington
- RE: [DUG]: DLLs Myles Penlington
- Re: [DUG]: DLLs Robert Martin