Re: can't bebug a dll

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joseph M. Newcomer (newcomer_at_flounder.com)
Date: 01/20/05


Date: Wed, 19 Jan 2005 23:38:16 -0500

Yes, but why do you care that the exe contains no debug information? Since you are
debugging the DLL, this message can obviously be ignored.

In VS6 you had to explicitly specify what DLLs you wanted, but I can't find a similar
feature in .NET 2003.

There are serious problems combining release MFC executables with debug MFC DLLs; you get
conflicts since you have two different MFC runtimes conflicting for resources. However,
you said the DLL is a simple windows sdk program, which is a set of terms which generally
don't fit together (MFC also uses the Windows SDK, for example); what I believe you are
saying is that the DLL is not an MFC-based DLL, so there should be no conflict when it is
used with an MFC executable, so the issues about the DLL being linked with an MFC debug
version don't make sense.
                                joe

On Thu, 20 Jan 2005 11:32:07 +0800, "msnews.microsoft.com" <_bandianxing_@hotmail.com_>
wrote:

>hello, all
> I am trying to debug a dll. The exe file is a mfc release version
>file, and the dll currently is a simple windows sdk program.
>My environment is windows XP, vc dotnet 2003, and I have set the exe as
>the debug commmand in the project-debug-debugging-command.
>While I debug the problem, the exe is executed, and report the the
>exe file contain no debug information. but the breakpoint in my dll is not
>effective. What may be the problem?
>
>And also, if the exe is a mfc release version , may I link the dll with
>mfc debug version? Is there some conflict?
>
>many thanks,
>PanTao
>

Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm



Relevant Pages

  • Re: newbie configuration questions
    ... When you say integrate multiple libraries, are you talking about 3rd party ... >> there is an MFC specific group microsoft.public.vc.mfc. ... >> the filename let's you know it's a debug DLL. ...
    (microsoft.public.vc.language)
  • Re: Static Dll vs Shared Dll
    ... > get link errors when building statically,. ... this is because you might have created an MFC extension DLL and not ... > I have 2 projects, one lib and the other is an exe, as usual I selected ...
    (microsoft.public.vc.mfc)
  • Re: Extension DLL with CDialog
    ... I have created an MFC Extension DLL, ... Compiled it both in release and debug mode.. ... MS closed the bug report ...
    (microsoft.public.vc.mfc)
  • Re: cant bebug a dll
    ... You cannot mix debug and release MFC environments without expecting serious disasters. ... other aids for debugging, but you have to give up something here. ... >> debugging the DLL, this message can obviously be ignored. ...
    (microsoft.public.vc.mfc)
  • cant bebug a dll
    ... I am trying to debug a dll. ... The exe file is a mfc release version ... My environment is windows XP, vc dotnet 2003, and I have set the exe as ...
    (microsoft.public.vc.mfc)