Blog Category for Func-eval

I created a blog category for Func-eval (aka Property Evaluation), and I updated some of my old posts to be in this category.

And while I’m at it, some other func-eval blog entries:
GreggM on Func-eval and Winforms
SteveJS on Nested Break States (stopping mid func-eval)

Update: Very *Evil* things you can do with funceval:
1. Funceval a message pump
2. Inject arbitrary code into another process.
3. Other evil things with FE

Here’s what’s involved for a debugger author to consume func-eval as part of inspection.

Comments (6)

  1. The ICorDebug API (the API for debugging managed apps) is about 70 total interfaces.  Here is how…

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

  3. Public Service Announcement: You may have noticed that trying to evaluate members using C#’s ‘base’ keyword…

  4. During native debugging, it’s common to cast a raw pointer value to a given type. Eg, in the expression…

  5. System.Object represents a managed object within a process. ICorDebugValue is the debugger’s representation…

  6. Here’s a list of things that may slow down execution under a debugger. I’ve seen a few threads go by