Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/Debugger/Interaction with IDE    [ Add a report in this area ]  
Report #:  6735   Status: Reported
Can't debug into a dll
Project:  C++BuilderX/BC++ 2005 Build #:  1.0
Version:    1.0 Submitted By:   Adam Versteegen
Report Type:  Basic functionality failure Date Reported:  1/2/2004 7:47:37 AM
Severity:    Commonly encountered problem Last Updated: 1/5/2004 9:17:38 AM
Platform:    All versions Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (1 Total Rating)
5.00 out of 5
Total Votes: 3
Description
At present it doesn't seem possible to debug a .dll in a straightforward manner...

Steps to Reproduce:
I found this:

Runtime Configurations When you run your application, the IDE uses a runtime
configuration to pass command-line parameters to the application. These
preset parameters save you time when running and debugging because you only
have to set the parameters once. You can use a runtime configuration to
specify a host executable for testing a .dll, or to load an executable into
the debugger. C++BuilderX comes with a default runtime configuration for
your application, but you can also edit the default or create your own

I looked in the runtime configurations and couldn't find an option for
'host' .exe. The only thing was 'project overrides' in which I could specify
an exe. Once i've setup the config, I can't find any way to make it active,
so I am still unable to 'run' my .dll.


Workarounds
My workaround:

The way i've been doing it is
to just debug from my main app, with the .dll and its tds in a folder
together. It means I can step into the .dll, but its not as convenient as
just being able to edit/compile/run straight from the .dll


From Maurice Barnume

what i've been doing (it works, it's not too convenient) is to use
"debug exectuable" to debug the host application; be sure to set up
the debug source paths in that project.  you should be able to set up
a project group such that the dll is built when you run the latter,
but i haven't bothered trying to do such a thing.
Attachment
None
Comments

Adam Versteegen at 1/2/2004 7:50:36 AM -
Add your comments here.

Build number for this bug is 1.0.1.103. I didn't know this off the top off my head, and unfortunately you cannot access the build number while the QC client launched from BCBX is open, as its BCBX doesn't receive any input.

Server Response from: ETNACODE01