November 11th, 2008, 10:31 AM
I've got a DLL that I'm trying to debug. I've inherited this code and cannot get in touch with the original developer to find out what to do.
This dll gets called to build a webpage. When I set a break point on the function getting called, the dll breaks just fine.
A bunch of Dim statements get called including
Then a bit later (the first actual line to debug)
Dim objContext As COMSVCSLib.ObjectContext
This isn't doing much of anything. objContext is not populated with anything.
Set objContext = GetObjectContext
The thing is, if I'm not debugging, everything works fine. I'm just trying to walk through the code to get a feel for the way things work. There's a ton of function calls and I do much better if I can walk through, ya know.
Does anyone have any ideas?
Someone suggested permission issues in the Component Services, which I've changed to include the IUSR, but that had no effect.
Thanks for your time.
I've debugged other DLLs for this application, none of them use COMSVCSLib though, so I think that's the main part of the problem.
Last edited by stin; November 11th, 2008 at 10:33 AM.
Reason: added clarification
Tags for this Thread
Click Here to Expand Forum to Full Width
This is a CodeGuru survey question.