471,610 Members | 1,369 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,610 software developers and data experts.

Debugger hell (7-18-2002)

There is an old thread I found on google where the OP was exhibiting the
same problems I am seeing.

Reference "Debugger hell" posted 7-18-2002 by Sean Gies

I am running Visual Studio 2003 RTM. Has this problem been fixed? I have a
C# application that calls a managed C++ wrapper of a native C++ dll.
Everything works fine. However, I notice on occasional breakpoints in my
native code, everything freezes and it takes a while to bring up TaskManager
to kill devenv. This is _really_ frustrating me and I am starting to worry
that this is going to delay our release date.

Any information is helpful.

-Drew
Nov 16 '05 #1
1 1357
Thanks Tian for the response. I will try your suggestions.

To answer your question about breakpoints and where and when this
problem occurs, it appears to be random. For instance, last week I had
set a breakpoint in my native C++ DLL. VS broke at a function and then
when I tried to step into the function, VS froze up and it took a
while to kill VS. I moved the breakpoint down past the function, and
it was better, although very slow. I notice when stepping through my
native code the debugger reacts very slowly, but when I am stepping
through my managed code it appears to be more responsive.

-Drew

ti******@online.microsoft.com (Tian Min Huang) wrote in message news:<JA**************@cpmsftngxa06.phx.gbl>...
Hello Drew,

Thanks for your post. I'd like to share the following information with you:

1. Please make sure that Enable Unmanaged Debugging for your C# project is
set to TRUE. Please right-click the C# project in Solution Explorer, select
Properties, and this option is under Configuration Properties -> Debugging.

2. Does this problem occurs to a specific (sets of) breakpoints in native
code or occurs to all breakpoints? As far as I know, we made some
improvements in interop-debugging in Visual Studio .NET 2003. However, this
issue is not totally resolved and it is being investigated.

To work around this problem, I suggest that you can debug the unmanaged DLL
seperately by the following steps:
a. Set the unmanaged DLL as Startup project in the solution.
b. Open the Property Page for the unmanaged DLL project.
c. Go to Configuration Properties -> Debugging, input the executable file
of C# in the Command edit box.
d. Press F5 will start the C# application which loads the unmanaged DLL,
and you can set breakpoints and debug it.

Please feel free to let me know if you have any problems or concern. I look
forward to hearing from you.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! C www.microsoft.com/security
This posting is provided as is with no warranties and confers no rights.

Nov 16 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

22 posts views Thread by Jim Hubbard | last post: by
1 post views Thread by Rhino | last post: by
1 post views Thread by GreatB | last post: by
reply views Thread by Clamps | last post: by
3 posts views Thread by Randy Magruder | last post: by
3 posts views Thread by Baron Samedi | last post: by
1 post views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by
reply views Thread by MichaelMortimer | last post: by
1 post views Thread by ZEDKYRIE | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.