🚀 go-pugleaf

Ok I got this working - I had to copy all my project files to the 
c:\Inetpub\scripts\ directory, and work out of there.

Not an ideal solution, but it works. Aparently C++ Builder 5 has difficultly 
attaching the debug symbols to DLLs which are output to any other directory 
other than the project dir.

Hope this helps anyone else having this problem.


"Robin Whitehead" <robin@whitehead.com> wrote in message 
news:41fe5f60@newsgroups.borland.com...
> Hi,
>
> I'm currently writing an ISAPI web service DLL. I am having problems 
> getting the debugger to work with this DLL.
>
> I have followed the instructions from the BDN (albeit about getting Delphi 
> ISAPI DLLs working with Windows 2000), and have successfully got IIS 
> working as a process.
>
> Everything seems to work fine - I can connect to my ISAPI dll, and it 
> behaves as expected - EXCEPT that the debugger is not breaking at any of 
> my break points. I have checked that I have all the debugging switched on, 
> and that the TDS file is written to the same directory as the DLL file.
>
> I am NOT getting any blue "dots" in the gutter in the BCB IDE when I press 
> "Run".
>
> Does anyone know how to get the debugger to "kick in" when writing an app 
> of this kind?
>
> I am using BCB5.0 (Build12.34) Update Pack 1, Windows XP SP2
>
> Cheers,
> Rob.
> 

> Not an ideal solution, but it works. Aparently C++ Builder 5 has
> difficultly attaching the debug symbols to DLLs which are output to
> any other directory other than the project dir.

Yes, it can be very annoying!  From memory, I believe another way around is 
to include the symbol file in your main project.

BCB6 resolves that problem but by and large I prefer BCB5...  It might be 
me but it certainly seems to crash less often!