|
|
You're in the
dotnet clr
group:Conditional Breaks
dotnet clr:
its value, set the breakpoint in the setter or method, and use the Call Stack window to locate the calling line.
Hi people,
Q: Is there a way to add a conditional break, so that execution breaks if the value of a variable changes. A: Yes there is, silly. Q: But I want execution to halt whenever that variable changes, in ANY line throughout my code, without having to set a gazillion breakpoints in every line that accesses that variable. A: .....anyone???? Jeppe Jespersen Denmark
[quoted text, click to view]
"McWawa" <jdj curlything jdj dot dk> wrote in message news:OSMljZd8GHA.2316@TK2MSFTNGP04.phx.gbl... > Hi people, > > Q: Is there a way to add a conditional break, so that execution breaks if > the value of a variable changes. > > A: Yes there is, silly. > > Q: But I want execution to halt whenever that variable changes, in ANY > line > throughout my code, without having to set a gazillion breakpoints in every > line that accesses that variable. > > A: .....anyone???? Does Debug -> New Breakpoint -> New Data Breakpoint... work for you? [quoted text, click to view] > > > Jeppe Jespersen > Denmark > > >
[quoted text, click to view]
> Does Debug -> New Breakpoint -> New Data Breakpoint... work for you? I believe that's only for unmanaged (native) code.
Then I would suggest that you implement the variable as a property and set
the breakpoint in the setter method. [quoted text, click to view] "McWawa" <jdj curlything jdj dot dk> wrote in message news:OSMljZd8GHA.2316@TK2MSFTNGP04.phx.gbl... > > Q: But I want execution to halt whenever that variable changes, in ANY > line > throughout my code, without having to set a gazillion breakpoints in every > line that accesses that variable. > > A: .....anyone???? >
[quoted text, click to view] > Encapsulate your variable into a class, use a property or a method to > change > its value, set the breakpoint in the setter or method, and use the Call > Stack window to locate the calling line. Thank you all. Jeppe Jespersen Denmark
I still don't have it clear...
Is there (or isn't) a way to set breakpoint on managed variable change? A property requires change of code and even than - you need to compare to previous value and set the breakpoint only if the new value is different When I debug production code using windbg + sos.dll - how can I break when, for example, an Int32 variable has changed value? And in Visual Studio? Loy [quoted text, click to view] McWawa wrote:
> > Encapsulate your variable into a class, use a property or a method to > > change > > its value, set the breakpoint in the setter or method, and use the Call > > Stack window to locate the calling line. > > Thank you all. > > Jeppe Jespersen > Denmark
RTM
http://msdn2.microsoft.com/en-us/library/350dyxd0.aspx What you want is a data breakpoint. These are only available in C++ navtive code . [quoted text, click to view] "Loy" <l.oyolox@gmail.com> wrote in message news:1161243543.773443.110810@h48g2000cwc.googlegroups.com... >I still don't have it clear... > > Is there (or isn't) a way to set breakpoint on managed variable change? > > A property requires change of code and even than - you need to compare > to previous value and set the breakpoint only if the new value is > different > > When I debug production code using windbg + sos.dll - how can I break > when, for example, an Int32 variable has changed value? > And in Visual Studio? > > Loy > > McWawa wrote: >> > Encapsulate your variable into a class, use a property or a method to >> > change >> > its value, set the breakpoint in the setter or method, and use the Call >> > Stack window to locate the calling line. >> >> Thank you all. >> >> Jeppe Jespersen >> Denmark >
[quoted text, click to view] "Noah Sham" <noahsham@verizon.net> wrote in message news:euWcU248GHA.4808@TK2MSFTNGP03.phx.gbl... > RTM > http://msdn2.microsoft.com/en-us/library/350dyxd0.aspx > > What you want is a data breakpoint. These are only available in C++ > navtive code . The essential problem here is that, even though the JIT turns your managed code into native code, and the processor debug registers allow you to break when a memory location is written, the garbage collector will move your variable here, there, and everywhere and not adjust the address in the debug register. Maybe you can find a way using a pinning pointer. Or you could use a (global static) gcroot, set a data breakpoint on that to find out when your variable gets moved around in the gc heap, and then update the data breakpoint on the variable. That breakpoint would be hit once each time the gc collects your generation -- so probably not much fun to track by hand. [quoted text, click to view] > > > "Loy" <l.oyolox@gmail.com> wrote in message > news:1161243543.773443.110810@h48g2000cwc.googlegroups.com... >>I still don't have it clear... >> >> Is there (or isn't) a way to set breakpoint on managed variable change? >> >> A property requires change of code and even than - you need to compare >> to previous value and set the breakpoint only if the new value is >> different >> >> When I debug production code using windbg + sos.dll - how can I break >> when, for example, an Int32 variable has changed value? >> And in Visual Studio? >> >> Loy >> >> McWawa wrote: >>> > Encapsulate your variable into a class, use a property or a method to >>> > change >>> > its value, set the breakpoint in the setter or method, and use the >>> > Call >>> > Stack window to locate the calling line. >>> >>> Thank you all. >>> >>> Jeppe Jespersen >>> Denmark >> > >
Thanks Ben and Noah
Seems like we need help from the sos.dll developers I know this is tricky due to heap compaction by the GC Your (Ben) point about memory hit by the GC itself is a good point I learned The complexity of this issue cry for help from Microsoft It would be highly appreciated if the next version of SOS will allow setting data breakpoint - and do all the necessary work to move the breakpoint and ignore GC itself reading the memory ... - behind the scenes I assume the same issue exists in Visual studio - and might explain why conditional breakpoints don't always work This is a needed tool while debugging and not having it make it harder to debug some issues in .net applications. Hope I'm not asking for too much Loy [quoted text, click to view] Ben Voigt wrote:
> "Noah Sham" <noahsham@verizon.net> wrote in message > news:euWcU248GHA.4808@TK2MSFTNGP03.phx.gbl... > > RTM > > http://msdn2.microsoft.com/en-us/library/350dyxd0.aspx > > > > What you want is a data breakpoint. These are only available in C++ > > navtive code . > > The essential problem here is that, even though the JIT turns your managed > code into native code, and the processor debug registers allow you to break > when a memory location is written, the garbage collector will move your > variable here, there, and everywhere and not adjust the address in the debug > register. Maybe you can find a way using a pinning pointer. Or you could > use a (global static) gcroot, set a data breakpoint on that to find out when > your variable gets moved around in the gc heap, and then update the data > breakpoint on the variable. That breakpoint would be hit once each time the > gc collects your generation -- so probably not much fun to track by hand. > > > > > > > "Loy" <l.oyolox@gmail.com> wrote in message > > news:1161243543.773443.110810@h48g2000cwc.googlegroups.com... > >>I still don't have it clear... > >> > >> Is there (or isn't) a way to set breakpoint on managed variable change? > >> > >> A property requires change of code and even than - you need to compare > >> to previous value and set the breakpoint only if the new value is > >> different > >> > >> When I debug production code using windbg + sos.dll - how can I break > >> when, for example, an Int32 variable has changed value? > >> And in Visual Studio? > >> > >> Loy > >> > >> McWawa wrote: > >>> > Encapsulate your variable into a class, use a property or a method to > >>> > change > >>> > its value, set the breakpoint in the setter or method, and use the > >>> > Call > >>> > Stack window to locate the calling line. > >>> > >>> Thank you all. > >>> > >>> Jeppe Jespersen > >>> Denmark > >> > > > >
Can someone from MSFT give us insight?
Loy [quoted text, click to view] Loy wrote:
> Thanks Ben and Noah > > Seems like we need help from the sos.dll developers > > I know this is tricky due to heap compaction by the GC > Your (Ben) point about memory hit by the GC itself is a good point I > learned > > The complexity of this issue cry for help from Microsoft > It would be highly appreciated if the next version of SOS will allow > setting data breakpoint > - and do all the necessary work to move the breakpoint and ignore GC > itself reading the memory ... - behind the scenes > I assume the same issue exists in Visual studio - and might explain > why conditional breakpoints don't always work > > This is a needed tool while debugging and not having it make it harder > to debug some issues in .net applications. > > > Hope I'm not asking for too much > > Loy > > > > > Ben Voigt wrote: > > "Noah Sham" <noahsham@verizon.net> wrote in message > > news:euWcU248GHA.4808@TK2MSFTNGP03.phx.gbl... > > > RTM > > > http://msdn2.microsoft.com/en-us/library/350dyxd0.aspx > > > > > > What you want is a data breakpoint. These are only available in C++ > > > navtive code . > > > > The essential problem here is that, even though the JIT turns your managed > > code into native code, and the processor debug registers allow you to break > > when a memory location is written, the garbage collector will move your > > variable here, there, and everywhere and not adjust the address in the debug > > register. Maybe you can find a way using a pinning pointer. Or you could > > use a (global static) gcroot, set a data breakpoint on that to find out when > > your variable gets moved around in the gc heap, and then update the data > > breakpoint on the variable. That breakpoint would be hit once each time the > > gc collects your generation -- so probably not much fun to track by hand. > > > > > > > > > > > "Loy" <l.oyolox@gmail.com> wrote in message > > > news:1161243543.773443.110810@h48g2000cwc.googlegroups.com... > > >>I still don't have it clear... > > >> > > >> Is there (or isn't) a way to set breakpoint on managed variable change? > > >> > > >> A property requires change of code and even than - you need to compare > > >> to previous value and set the breakpoint only if the new value is > > >> different > > >> > > >> When I debug production code using windbg + sos.dll - how can I break > > >> when, for example, an Int32 variable has changed value? > > >> And in Visual Studio? > > >> > > >> Loy > > >> > > >> McWawa wrote: > > >>> > Encapsulate your variable into a class, use a property or a method to > > >>> > change > > >>> > its value, set the breakpoint in the setter or method, and use the > > >>> > Call > > >>> > Stack window to locate the calling line. > > >>> > > >>> Thank you all. > > >>> > > >>> Jeppe Jespersen > > >>> Denmark > > >> > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |