Rules of Funceval

re: Rules of Funceval

Sam — Fri, 16 Dec 2005 07:10:21 GMT

Odd I get a "Cannot evaluate expression because the code of the current method is optimized." on a Debug.Assert statement, this seems like a problem in the design. Debug.Assert should not be optimised for debug builds ...

re: Rules of Funceval

jmstall — Fri, 16 Dec 2005 23:46:40 GMT

Sam - good ovservation. It's worthy of its own blog post. Stay tuned...

re: Rules of Funceval

Max C — Tue, 07 Feb 2006 14:39:49 GMT

We're having the same problem as Sam here.

What does a debugger author need to do to support func-eval?

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

I've mentioned func-eval (aka property eval) is evil for end-users; but it's also evil if you want to...

Trivia about Set-next-Statement (SetIp)

Mike Stall's .NET Debugging Blog — Wed, 22 Mar 2006 06:31:19 GMT

The poor-man's version of Set-Next-Statement (aka, SetIp) is to just forcibly set the instruction pointer...

Func-eval can fail while stopped in a non-optimized managed method that pushes more than 256 argument bytes

Rick Byers — Sun, 17 Aug 2008 02:59:03 GMT

In this blog entry , Mike describes that func-eval will fail when not a GC-safe point. In VS this results

Func-eval can fail while stopped in a non-optimized managed method that pushes more than 256 argument bytes

Rick Byers — Sun, 17 Aug 2008 02:59:44 GMT

In this blog entry , Mike describes that func-eval will fail when not a GC-safe point. In VS this results

Cannot evaluate expression because a thread is stopped at a point where garbage collection is impossible, possibly because the code is optimized - can be caused by Large function calls

Avi Pinto — Sun, 15 Mar 2009 01:28:46 GMT

בעיית design/debugging מרגיזה, שנתקלתי בה בעבר: נתון קוד קיים, שעובד ב production והיה צורך להוסיף פונקציונליות