You just need to compile with TD32 debug info - on linker tab of project
options.
The other think is to specify a different base loading address - one that
does not cause a relocation of the DLL. You can also debug your DLL from
within delphi by starting IIS as a process - much easier.
Have a look at this - documents how to run IIS as a process - I also see
there is now similar info on the borland community site.
http://www.fulgan.com/delphi/index.asp
> -----Original Message-----
> From: Blackie, Nikolai [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 17, 2000 1:44 PM
> To: Multiple recipients of list delphi
> Subject: [DUG]: Loading DLL Debug Symbols for IIS Exception Monitor
>
> Hi all, has anyone had experience developing Delphi objects for ASP and
> come
> across the dreaded ASP0115 error? I have been running IIS Exception
> Monitor,
> a M$ utility for catching errors and all stack info, to try and narrow
> down
> exactly which DLL function is corrupting the heap.
> http://msdn.microsoft.com/workshop/server/iis/ixcptmon.asp
>
> The main problem I am having is loading the debug symbols for my DLL's so
> that I can find the exact function, else I am left with a memory address
> which ain't that helpful. Anyone here used this utility and know how to
> produce and load the symbols?
>
> Nikolai Blackie
> Business Education On-Line
>
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
