debug a DLL in VC++ 2005

Question

0.00/5 (No votes)

See more:

Hello,

I have a DLL written in VC2005 and a testprog to test the DLL.. i m wondering how can i debug the DLL using bring point ??

I run the DLL (by hitting F5) and i gave it the path of the exe (the testapp one) but the app runs withour debuggin (it jumped the breakpoint/ the breakpoint became desactivated).

could someone help me !! Thank you

Posted 13-Jan-12 10:41am

Schehaider_Aymen

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Addy Tas · Accepted Answer · 2012-01-13T10:57:00

Solution 1

Hi,
I can't really advice mixing release and debug versions but: yes it is possible. I do need to use simular constructs on a regular base as well. If the breakpoints are removed it is very likely that you are not actually using the current output or better said, it can't find the objects. Easyest way to test this is to copy the exe to the debug output folder and run it from there. It would at least make sure that all the pdb's, obj etc. Files can be located.

Hope this helps,

Cheers, AT

Posted 13-Jan-12 10:57am

Addy Tas

Comments

Schehaider_Aymen 13-Jan-12 17:27pm

That solved the problem. but Could u explain me what was the matter when i gave them the path of the exe !!! (the first scenario that i gad prob witgh)

Addy Tas 13-Jan-12 17:37pm

Naturally i can't give you a 100% answer but I'll give it a try.
Option one: you have another copy of the dll next to the exe.
Option two: there is another copy of the dll on a location that is earlier in the Systems Path
Option three: you copy the output to the exe's location. Running this version is ok but without the symbols file the debugger can't really do with it.

I guess these are my two cents for now...

If you feel like it; don't forget to upvote :)

Cheers, AT

Schehaider_Aymen 13-Jan-12 17:45pm

I guess i m in the 3rd option : I redirected the output of the DLL project to the TestApp Exec (in the Debug Folder) but i did not create the symbols file .. it s my first time that i create a DLL (i ll mae sure to read more about all that stuff) Thk You Addy, u were very helpfull

Addy Tas 13-Jan-12 17:49pm

Hi,

This is what you want to know: http://msdn.microsoft.com/en-us/library/yd4f8bd1(v=vs.71).aspx

Cheers, AT

Schehaider_Aymen 13-Jan-12 17:50pm

Thank you.