By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,115 Members | 894 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,115 IT Pros & Developers. It's quick & easy.

DEBUG fails to trap/catch on breakpoint...

P: n/a
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
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp

Nov 19 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
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...en-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
Nov 19 '05 #2

P: n/a
ASP.NET debugging is enabled and you're correct, there aren't any error
messages that popup... it just never seems to really attach to the debug
process. The PDB files are there and have the same timestamp as the DLL's.

ANy other ideas?

--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"Craig Deelsnyder" <cdeelsny@NO_SPAM_4_MEyahoo.com> wrote in message
news:ui*************@TK2MSFTNGP12.phx.gbl...
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...en-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

Nov 19 '05 #3

P: n/a
I forgot to mention this is Win2003 *SP1*, but I am pretty sure this was
happening before SP1 as wel.

--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"AC [MVP MCMS]" <sw*********@gmail.com> wrote in message
news:eV**************@TK2MSFTNGP10.phx.gbl...
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
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp

Nov 19 '05 #4

P: n/a
Make sure when you attach to the process that the Common Language Runtime
option is checked in the dialog that opens after you hit attach.

bill

"AC [MVP MCMS]" <sw*********@gmail.com> wrote in message
news:uu****************@TK2MSFTNGP14.phx.gbl...
ASP.NET debugging is enabled and you're correct, there aren't any error
messages that popup... it just never seems to really attach to the debug
process. The PDB files are there and have the same timestamp as the DLL's.
ANy other ideas?

--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"Craig Deelsnyder" <cdeelsny@NO_SPAM_4_MEyahoo.com> wrote in message
news:ui*************@TK2MSFTNGP12.phx.gbl...
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...en-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


Nov 19 '05 #5

P: n/a
Yup... done that... still no luck...
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"William F. Robertson, Jr." <th****@nameht.org> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
Make sure when you attach to the process that the Common Language Runtime
option is checked in the dialog that opens after you hit attach.

bill

"AC [MVP MCMS]" <sw*********@gmail.com> wrote in message
news:uu****************@TK2MSFTNGP14.phx.gbl...
ASP.NET debugging is enabled and you're correct, there aren't any error
messages that popup... it just never seems to really attach to the debug
process. The PDB files are there and have the same timestamp as the

DLL's.

ANy other ideas?

--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"Craig Deelsnyder" <cdeelsny@NO_SPAM_4_MEyahoo.com> wrote in message
news:ui*************@TK2MSFTNGP12.phx.gbl...
> 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...en-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



Nov 19 '05 #6

P: n/a
Little more info to make it even more wierd:

Manually attaching to the w3wp.exe didn't work (skipps the breakpoint).

Automatically jumping into debug mode by hitting F5 does stop at the
breakpoint.

Have opened a PSS case on this and will post my results.

--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"AC [MVP MCMS]" <sw*********@gmail.com> wrote in message
news:eV**************@TK2MSFTNGP10.phx.gbl...
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
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp

Nov 19 '05 #7

P: n/a
It was such an obscure fix, I decided to throw it up on my blog for others
who may have this issue.
http://andrewconnell.com/blog/archiv...5/30/1278.aspx
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp
"AC [MVP MCMS]" <sw*********@gmail.com> wrote in message
news:eV**************@TK2MSFTNGP10.phx.gbl...
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
--
----------------------------------------
-AC [MVP MCMS]
www.andrewconnell.com
www.andrewconnell.com/mvp

Nov 19 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.