Func-eval is evil

re: Func-eval is evil

Junfeng Zhang — Wed, 23 Mar 2005 08:39:00 GMT

Windbg added func-eval in 6.4. That means something.

Just don't turn it on by default.

re: Func-eval is evil

Mike Stall — Wed, 23 Mar 2005 09:23:00 GMT

Junfeng - true, though it's interesting to drill into that further.

Windbg's funceval is for native code only, not managed. Visual Studio has also had func-eval for native-code since at least V6.0 (don't know exactly when it first appeared).

Both those cases of func-eval must be explicitly invoked by the user (contrast to VS's auto evaluation of managed property-getters and ToString() calls). That mitigates issues 2,3,4.
Windbg also mitigates issue #1 by giving the end-user full control over the funceval.

re: Func-eval is evil

Mark Mullin — Wed, 23 Mar 2005 17:43:00 GMT

Yeah, the whole things been a pet peeve of mine too. I have some classes that have exceptionally complex properties and I want them to stay properties - that said, if I've got some problem in spinning up the class, I can run smack into this

I know about the ui setting to suppress this, what I'd love, at least in managed C#, is an attribute I can attach to individual properties to suppress evaluation = far better than the all or nothing option I have at present.

re: Func-eval is evil

Mike Stall — Wed, 23 Mar 2005 18:14:00 GMT

Mark - I think VS actually has a ton of attributes that you can place on properties and classes to give VS better hints as to how to display them and what to avoid func-evalling on. Andy P. mentioned one that may do exactly what you want:
DebuggerBrowsable.Never

I'll see if I can dig up more about this.

.NET property evaluation while debugging is BAD, BAD, BAD

Bring It On — Mon, 01 Aug 2005 14:34:38 GMT

.NET property evaluation while debugging is BAD, BAD, BAD

Bring It On — Mon, 01 Aug 2005 14:35:32 GMT

.NET property evaluation while debugging is BAD, BAD, BAD

Bring It On — Mon, 01 Aug 2005 14:41:28 GMT

Example of Goofy bugs

Mike Stall's .NET Debugging Blog — Sat, 03 Sep 2005 02:01:19 GMT

Here's an sampling of various goofy bugs we've had to deal with in the CLR Debugging services over the...

Out-of-band events and Mixed-mode debugging

Mike Stall's .NET Debugging Blog — Tue, 13 Sep 2005 18:10:13 GMT

Interop-debugging splits all debug events into "In-band (IB) " and "Out-of-band (OOB)". Inband events...

Blog Category for Func-eval

Mike Stall's .NET Debugging Blog — Sun, 05 Mar 2006 20:49:01 GMT

I created a blog category for Func-eval&nbsp;(aka Property Evaluation), and I updated some of my old...

Eli Lopian’s Blog (TypeMock) » Blog Archive » How to Debug with TypeMock.NET without losing your head

Wed, 11 Oct 2006 10:33:25 GMT

PingBack from http://www.elilopian.com/2006/10/08/how-to-debug-with-typemocknet-without-losing-your-head/

Func-eval abort is evil

Mike Stall's .NET Debugging Blog — Wed, 14 Mar 2007 03:38:32 GMT

Func-eval is evil . Func-eval abort is even worse. For those coming in late, Func-eval is when the debugger