C++/VB - MS 2005 Debugger - pathetically slow

Hi,
My VS2005 IDE debugger runs extremely slow, how can I make it run faster? it
takes 1-2 mins per breakpoint to get hit.
Thanks
Jack

  Jack replied...

Re-compile to no avail. Where elses can I check?
Thanks
Jack

  David Lowndes replied...

Clearly the behaviour you're seeing isn't normal.

If you create a new console application and debug that (on the same
machine you have VS installed on), do you still see the same issue?

Assuming you don't, what is the application you're debugging? Is it
native C++, or managed C++? What sort of environment is it running in?
Is it on a separate machine, is there network communications (that may
have some timeout) involved somewhere?

Dave

  Jack replied...

Hi David,
Sorry for the late reply.
I now think that the slow response is because of the unalignment of the
breakpoint and the source code...
Any chances that might happen?
Thanks
Jack

  David Lowndes replied...

Jack,

I do not understand what you are theorising there.

Have you tried deleting all the breakpoints?

Dave

breakpoint when a variable has changed C++ / VB Hello How can I set a breakpoint that stops the program when a variable has changed its value? Thanks Cathy VC Debugger Discussions SomeVariable (1) DevStudio (1) Nathan (1) Mates (1) Breakpoint (1) Window (1) VS2005 (1) Times (1) You can't. But: In the VS2005 debugger you can right-click on a breakpoint and add a [Condition] or [Hit count], so you can stop at the assignment of written to. As such, they're not easy to use if you're trying to breakpoint a variable on the stack, as the stack's memory addresses are generally recycled from function to function. To set a breakpoint, do the following: 1) Obtain the address you wish to breakpoint at. I generally do

Converting VC6 Project to VS2005 - Warning Message C++ / VB When opening a VC6 (MFC) project in VS2005 I get the following warning, project format. After it has been converted, you will not Convert and open the project?" This warning appears each time I open the project with VS2005, and contrary to the warning I have found that I am indeed able to edit explain why this warning appears, why it appears each time I open the project in VS2005, and if there may be some caveats to be aware of while I maintain projects temporarily under both VC6 and VS2005 (eventually porting them to VS2005). In a previous related post, David W. advised me to use separate output directories for VC6 and VS2005, but this question relates more specifically to this warning message, and how VS2005 maintains the project (which is why I am asking this question under a new thread

Why it can not work after I delete breakpoint.(attach the CSocketFile object to a CArchive) C++ / VB class CChatSocket : public CSocket { . . . } void CChatSocket::OnReceive(int nErrorCode) { CSocket::OnReceive(nErrorCode); / / Here I insert a breakpoint, m_pDoc-> ProcessPendingRead(); } It works well if I insert a breakpoint int the CHATTER (Client). but If I delete that breakpoint, OnReceive function can not receive anything.(of course CHATSRVR have the breakpoint too.the onlye changing is breakpoint) the source code is in MSDN (CHATTER and CHATSRVR) VC MFC Discussions CMyOwnSocket (1) ProcessPendingRead be at *most* one character, even though you sent 24, 000. The nature of the breakpoint is that you have changed the timing of your program. So the kernel stacks are still receiving data but without the breakpoint, you get to the data too soon relative to what is really going on. Please

Our VS2008sp1 Release builds crash badly. . . C++ / VB Friends, We build our large application using VS2005 in both Release / Debug configruations and everything functions as expected. VS2008sp1 Debug builds seem to is hard because problems do not appear in our Debug builds or any of our VS2005 builds. All necessary SxS DLLs are in place for both MFC / ATL / C run-times for versions 8, 9.02 and 9.03. Our projects were converted from VS2005 to VS2008 automatically by VS2008, so all the project options remain identical. Did something major good old fashioned bugs or coding errors. For now, our QA folks are tsting a VS2005 build, but we are set to release with a VS2008 build. I'm at a yet, although we use TCHAR all over the place. I just don't understand why VS2005 compilation result in a perfectly function application and VS2008 does not. Sure there might be code around, this application is huge, but things have been rock solid for years with VS2005. I'll try to debug a Release build since the Debug build works well; I compiler and settings? -cd Thanks Carl, I'll go check everything. (It all worked under VS2005, and we have not changed any project settings; we just let VS2008 upgrade the projects and then built the solution. But, maybe we were just lucky in VS2005, who knows.) James Using a hint from Carl, I compiled a release build one of

respond to top-posted replies, please do not ask I put cout line after the breakpoint, I can see cout print out, but the program went through breakpoint without stop. So it got run. thanks Here is the process exe is C# compiled the dll codes from C# exe project without problems, ONLY IF I set the starting breakpoint in C#. Howwever, though I set breakpoint in C++ dll in the same method, my program will not stop there (regardless different thread or not, just found it). One thing I just found, if I set breakpoint at C# codes, I can actually step into the C++ dll codes. If I set breakpoint in the same method of my C++ codes, program will not stop. I think maybe windows options in VS2008. Thanks Chris correction. I made one mistake. Instead, if I set breakpoint in that call method, regardless in c# or in c++ dll, it works. Breakpoint does not work ONLY if I put it in that timer thread codes. Though I