Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The source for the Winforms GUI extension to MDbg is now available as a sample. (Sorry it took so long).
The download is available here.
I’ve also updated the original post with this link.
Here's a screenshot of the updated gui:
Comments
- Anonymous
February 05, 2005
Good job. - Anonymous
February 08, 2005
I'm interested in your opinion of what implementing support for debugging custom languages (e.g. a code generator input language or a server-side scripting language) would entail. A bit like JSR-45 for the .NET platform essentially.
JSR-45 is here:
http://www.jcp.org/en/jsr/detail?id=45
Martin - Anonymous
February 08, 2005
Martin - the CLR already supports cross-language debugging (as part of .NET's overall cross-language interopability story).
Basically, anything you can compile to IL, we can debug for free.
I recently posted an example of this for reflection-emit: http://blogs.msdn.com/jmstall/archive/2005/02/03/366429.aspx - Anonymous
February 08, 2005
The comment has been removed - Anonymous
February 08, 2005
Martin: that's an excellent question.
What you want is the ability to debug an arbitrary table-driven state-machine, right?
So the current source file / callstack (and maybe even locals, etc) would be calculated based off the state machine's current state, and not the actual underlying code that the state machine was running, right? - Anonymous
February 08, 2005
The comment has been removed - Anonymous
March 03, 2005
This question likely reflects a lack of understanding on my part. When I use MDbg Winforms GUI to attach to a running process, I can the list of loaded modules (some of them which say symbols loaded) but I always get the message "No source for current thread". What am I missing to be able to debug? Ideally I'd like to "IL-debug" if that's possible. - Anonymous
March 03, 2005
Notre -
1) The process is stopped, right? If not, try "Debug | Break".
2) Are there symbols loaded for the modules that you want to see source for on the stack?
3) Can you get a stack trace from the command prompt in the gui?
Note that the gui doesn't support debugging at the IL-level. - Anonymous
March 04, 2005
The comment has been removed - Anonymous
March 04, 2005
The comment has been removed - Anonymous
March 04, 2005
Thanks Mike! I figured out what was wrong and it was a user error; after attaching to the process and setting my breakpoints, I failed to issue the "go" command. After this, managed debugging worked just fine. Ironically, I figured out what I was doing wrong by playing with MDbg itself rather than using the GUI; I was able to apply the same principles in the GUI after figuring it out in MDbg.
I will review your small peak blog. I'd love to see anything else you write about IL debugging in the future. - Anonymous
June 02, 2005
I had a sample GUI extension for Mdbg Beta 1. However, it doesn’t build with Mdbg Beta 2 because:   ... - Anonymous
August 10, 2005
I had a sample GUI extension for Mdbg Beta 1. However, it doesn’t build with Mdbg Beta 2 because:   ... - Anonymous
August 18, 2005
I had a sample GUI extension for Mdbg Beta 1. However, it doesn’t build with Mdbg Beta 2 because:   ... - Anonymous
September 14, 2005
ICorDebug (ICD) is a com-classic interface. In terms of COM threading models, ICorDebug is technically... - Anonymous
June 18, 2006
PingBack from http://blogs.msdn.com/jmstall/archive/2005/11/08/mdbg_linkfest.aspx - Anonymous
May 18, 2007
Here's my first Silverlight 1.1 (which has .NET support) app. It bounces various shapes around the canvas.