RE: VS.NET 2003, often won't stop at breakpoints, at wits end!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi,
We've seen same problem recently with native c++ program.
Do you have any other debug/profile tools installed, like Compuware
devpartner?

--PA

"Matt Greer" wrote:
> Hello,
>
> I post this message in desperation. Not stopping at breakpoints while
> debugging is a very common problem with my use of VS.NET 2003 and I'm
> hoping someone can shed some light.
>
> I am using:
> -- Visual Studio.NET 2003 version 7.1.3088
> -- Windows XP Pro, with Service Pack 2, version 5.12600 build 2600
> -- Coding in C#
>
> I am already sure that:
> -- I am running in Debug mode
> -- Generation Debugging Information is true for all projects
> -- the DEBUG preprocessor constant is defined
> -- The breakpoint is enabled
> -- The breakpoint should be traversed (ie that section of code really
> is executed)
> -- the pdb file for the assembly is present in the same directory as
> the assembly and exactly corresponds to that version of the assembly.
> -- The Modules window shows the assembly is loaded and with symbols.
>
> Also:
> -- I have cleared the VS cache under <username>/local
> settings/application data/assembly
> -- I've completely wiped my local copy of the project and re-obtained
> it from source control
> -- and even more, this computer was recently formatted and reinstalled
> with a fresh copy of Windows and VS.NET
>
> And finally :) :
> -- It appears to be totally random. My solution contains a mixture of
> native and .NET projects. I can get it to stop at breakpoints in
> certain projects just fine. If I attempt to start debugging from a
> project that is wokring ok and attempt to step into the problem
> project, I get a "No source code is available at this location" error.
> -- Coworkers working on the same project have no problem debugging on
> their machines.
>
>
> I have this problem all the time. And the solution almost always seems
> to be completely random. Sometimes rebooting my machine does it.
> Sometimes relaunching VS. Sometimes switching over to release and back
> to debug mode. But no solution ever seems to work reliably. It's
> driving me crazy and really making me wish I had a job coding in Java
> :)
>
> Thanks for any ideas,
> Matt
>
>
.



Relevant Pages

  • VS.NET 2003, often wont stop at breakpoints, at wits end!
    ... Not stopping at breakpoints while ... debugging is a very common problem with my use of VS.NET 2003 and I'm ... their machines. ... to debug mode. ...
    (microsoft.public.vsnet.general)
  • Re: Breakpoints are not getting hit in ASP.NET (C#) project
    ... Check Machine Debug Manager is working. ... Continued to my earlier post regaring "Breakpoints are not getting hit" ... I am getting the following error while debugging any newly created ... · Very first time there was nothing selected in the "choose the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VS .NET not breaking on breakpoints
    ... try to start debugging with F10. ... where the problematic breakpoints are set (if the application's design ... Will the proper source code be shown? ... > F5 the execution still does not break on the breakpoints. ...
    (microsoft.public.vc.debugger)
  • Re: Object reference not set to an instance of an object
    ... can't help you with the assembler code. ... Check the callstack, check parameter values ... Try debugging the design time ... >> breakpoints in your code and examine its data etc. ...
    (microsoft.public.dotnet.framework.windowsforms)