Re: DEBUG fails to trap/catch on breakpoint...

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

AC [MVP MCMS] wrote:
Wierd situation here. Running ASP.NET 1.1 on Win2003. I have to manually attach the debugger to a process in order to debug. So I set a breakpoint in an obvious place (like within the Page.Load event) that will catch it. For Win2003, I attach to the w3wp.exe process.

I've made sure my project is building as DEBUG.
I've made sure the breakpoint it reachable.
I've made sure my web.config has debug=true.

But when I run through the page, the breakpoint remains with the question mark within the left margin of the code behind.

Why wouldn't VS.NET break on the breakpoint? Based on the question mark in the margin, I'm assuming VS.NET isn't attaching to the process. What could cause this?

Thanks in advance

Refresh my memory (I don't have a PC w/ VS handy), is this setting tied to web.config (i.e. updates it)?:

http://support.microsoft.com/kb/306169/EN-US/

If so, meaning it's not a solution for you, I would first verify when you build the debug version that the pdb files are created in the same location as your dll(s). Otherwise, the motherload of most problems like this can be found here:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B306172

although most of those problems would result in your seeing an error dialog box, which I didn't hear you mention.

--
Craig Deelsnyder
Microsoft MVP - ASP/ASP.NET
.

Relevant Pages

  • Re: DEBUG fails to trap/catch on breakpoint...
    ... The PDB files are there and have the same timestamp as the DLL's. ... >> manually attach the debugger to a process in order to debug. ... >> I've made sure the breakpoint it reachable. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: DEBUG fails to trap/catch on breakpoint...
    ... Make sure when you attach to the process that the Common Language Runtime ... >>> manually attach the debugger to a process in order to debug. ... >>> I've made sure the breakpoint it reachable. ... >>> in the margin, I'm assuming VS.NET isn't attaching to the process. ...
    (microsoft.public.dotnet.framework.aspnet)
  • DEBUG fails to trap/catch on breakpoint...
    ... I attach to the w3wp.exe process. ... I've made sure my project is building as DEBUG. ... I've made sure the breakpoint it reachable. ... the margin, I'm assuming VS.NET isn't attaching to the process. ...
    (microsoft.public.dotnet.framework.aspnet)
  • DEBUG fails to trap/catch on breakpoint...
    ... I attach to the w3wp.exe process. ... I've made sure my project is building as DEBUG. ... I've made sure the breakpoint it reachable. ... the margin, I'm assuming VS.NET isn't attaching to the process. ...
    (microsoft.public.vsnet.debugging)
  • Re: [RFC] hwbkpt: Hardware breakpoints (was Kwatch)
    ... Debug exceptions don't occur very often, and when they do it won't ... The global kernel allocations will already be set in the processor from the ... CPU 1 goes in and alters the user breakpoint data, ... * Hardware breakpoints are implemented using the CPU's debug registers, ...
    (Linux-Kernel)