Debugging DLL in VC6

Question

1.00/5 (2 votes)

See more:

I'm worried about debugging DLL.
My development environment is VC6, the progran is consist by a master screen program and multiple DLL.
The problem is that most of the DLL can be debugged, and some of them can be debugged occasionally, and I don't know what to do. Can you give me what is the reason?

What I have tried:

1. Verify that the output of all DLL and main programs is configured in the same directory
2, PDB files are also exported to the directory at the same time
3. The DLL dependencies DLLs is the same configuration

Posted 28-Mar-18 15:17pm

ningcai

Updated 28-Mar-18 23:28pm

Add a Solution

Comments

Patrice T 28-Mar-18 22:20pm

What are you talking about? This makes no sense.
Remember that we are not in your head.

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)

KarstenK · Answer 1 · 2018-03-28T23:29:00

It is a bit unspecific but you do the right things.

a) Check that all dll are build in debug mode, all actual pdb are in the app directory. Set the output dir of the dlls to the app directory
b) Check that the app has the app directory as startup directory (setting of the project) and the dll from that directory are used. In some cases dlls from other pathes get used when they are in the search path.
c) Delete all your unused project dlls in other directories. But only these!!!
d) Use a more modern version of Visual Studio.
e) Use the famous and mighty Dependency Walker which is your best friend in "dll hell".