Debugging DLL problem
-
Hello, I've got a little problem when I want to debug my DLL. The situation is as follows: - I've a DLL project and I've buildt a debug version of the DLL with the PDB file. - I've another project and I want to test the DLL by calling it's functions with predefined data. When I hit a application breakpoint, I want to step into the DLL's code. - The DLL and the PDB are in the same folder as the test application. The problem is that VS2005 says that no debug symbols are loaded for the DLL. Is there a way to load those symbols manually, or am I doing something wrong? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
-
Hello, I've got a little problem when I want to debug my DLL. The situation is as follows: - I've a DLL project and I've buildt a debug version of the DLL with the PDB file. - I've another project and I want to test the DLL by calling it's functions with predefined data. When I hit a application breakpoint, I want to step into the DLL's code. - The DLL and the PDB are in the same folder as the test application. The problem is that VS2005 says that no debug symbols are loaded for the DLL. Is there a way to load those symbols manually, or am I doing something wrong? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
I have not done any DLL debugging with VS2005 yet, however in the past to get a DLL to step debug I had to start the debugger from the DLL project specifying the EXE that will load the DLL. If you cannot get the EXE to stop at the point you wish, just put an "_asm int 3h" inline and the debugger will stop. If its a debug build it should automatically pull in the source.
-
Hello, I've got a little problem when I want to debug my DLL. The situation is as follows: - I've a DLL project and I've buildt a debug version of the DLL with the PDB file. - I've another project and I want to test the DLL by calling it's functions with predefined data. When I hit a application breakpoint, I want to step into the DLL's code. - The DLL and the PDB are in the same folder as the test application. The problem is that VS2005 says that no debug symbols are loaded for the DLL. Is there a way to load those symbols manually, or am I doing something wrong? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
Bob Stanneveld wrote:
The DLL and the PDB are in the same folder as the test application.
Are they in the directory for the test applications project or are they located in the Debug sub-directory? If I remember correctly they should be in the Debug sub-directory. Chris Meech I am Canadian. [heard in a local bar] Remember that in Texas, Gun Control is hitting what you aim at. [Richard Stringer] Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me]
-
Hello, I've got a little problem when I want to debug my DLL. The situation is as follows: - I've a DLL project and I've buildt a debug version of the DLL with the PDB file. - I've another project and I want to test the DLL by calling it's functions with predefined data. When I hit a application breakpoint, I want to step into the DLL's code. - The DLL and the PDB are in the same folder as the test application. The problem is that VS2005 says that no debug symbols are loaded for the DLL. Is there a way to load those symbols manually, or am I doing something wrong? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
there are two ways i handle this: 1. put the DLL project into the same solution/workspace as your app, build the DLL and the app. then the debugger will know how to find the DLL source. or 2. in your DLL project, set your test app as the startup EXE . then when you 'run' the DLL, it will start the test app, and you can put breakpoints in the DLL (but not in the test app). Cleek | Image Toolkits | Thumbnail maker
-
I have not done any DLL debugging with VS2005 yet, however in the past to get a DLL to step debug I had to start the debugger from the DLL project specifying the EXE that will load the DLL. If you cannot get the EXE to stop at the point you wish, just put an "_asm int 3h" inline and the debugger will stop. If its a debug build it should automatically pull in the source.
-
Bob Stanneveld wrote:
The DLL and the PDB are in the same folder as the test application.
Are they in the directory for the test applications project or are they located in the Debug sub-directory? If I remember correctly they should be in the Debug sub-directory. Chris Meech I am Canadian. [heard in a local bar] Remember that in Texas, Gun Control is hitting what you aim at. [Richard Stringer] Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me]
-
there are two ways i handle this: 1. put the DLL project into the same solution/workspace as your app, build the DLL and the app. then the debugger will know how to find the DLL source. or 2. in your DLL project, set your test app as the startup EXE . then when you 'run' the DLL, it will start the test app, and you can put breakpoints in the DLL (but not in the test app). Cleek | Image Toolkits | Thumbnail maker
Hello, Thanks for your reply. :-D
Chris Losinger wrote:
1. put the DLL project into the same solution/workspace as your app, build the DLL and the app. then the debugger will know how to find the DLL source.
The projects are all in the same solution. I even pointed the target directory of the GUI test app to the general debug folder where VS puts all the libraries.
Chris Losinger wrote:
2. in your DLL project, set your test app as the startup EXE . then when you 'run' the DLL, it will start the test app, and you can put breakpoints in the DLL (but not in the test app).
I also did this, but it didn't work. Is this a missing feature in the standard edition? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
-
Hello, Thanks for your reply. :-D
Chris Losinger wrote:
1. put the DLL project into the same solution/workspace as your app, build the DLL and the app. then the debugger will know how to find the DLL source.
The projects are all in the same solution. I even pointed the target directory of the GUI test app to the general debug folder where VS puts all the libraries.
Chris Losinger wrote:
2. in your DLL project, set your test app as the startup EXE . then when you 'run' the DLL, it will start the test app, and you can put breakpoints in the DLL (but not in the test app).
I also did this, but it didn't work. Is this a missing feature in the standard edition? Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
could be a vs05 issue, but since i've never used vs05, i can't say... Cleek | Image Toolkits | Thumbnail maker
-
could be a vs05 issue, but since i've never used vs05, i can't say... Cleek | Image Toolkits | Thumbnail maker
I think that it's a missing feature in the standard edition. I think that the content of the debug output window is the output of dr watson. This output says that the debug symbols are loaded, but when I hold the cursor above the DLL breakpoint, the tooltip says that there are no symbols loaded. :confused: I have to verify this somehow. Behind every great black man... ... is the police. - Conspiracy brother Blog[^]