Freigeben über

VS 2003 Tip #16: Part I - Free debuggers

  • Artikel

Quick - what are the two free managed debuggers that you can get in Everett (not counting VS 2003)? And if you do know the answer (which I'm fairly certain most do) why do you use them over VS 2003? Let me know what scenarios or why!

Comments

  • Anonymous
    April 21, 2004
    cordbg and dbgclr

    Guess there's 3: you forgot windbg with sos.dll :)

    Use cordbg all the time :)
  • Anonymous
    April 21, 2004
    Nice, but why do you use cordbg all the time?
  • Anonymous
    April 21, 2004
    I use cordbg to see the optimized x86 output from the JIT.
  • Anonymous
    April 21, 2004
    I for one did not know that there were other managed debuggers, nor why I would want to use one :(

    Marcie
  • Anonymous
    April 21, 2004
    I'm in the same boat as Datagrid girl. Can someone give a few mode use cases to illustrate when an alternative debugger would be useful?
  • Anonymous
    April 21, 2004
    The comment has been removed
  • Anonymous
    April 22, 2004
    One more reason for cordbg: You can debug a fully optimized program. VS.NET doesn't allow you to do that.

    I'll also echo Pavel's comment about debugging on other machines. Many times (usually on Win98) I've (and people I work with have) run into issues where the app crashes oddly and it can't be reproduced on a dev machine. The other debuggers are extremely useful at times like this.
  • Anonymous
    May 16, 2004
    What I want in a debugger is to watch every thread, if I break @ a breakpoint, I would like to be able to see a threadview and see where every thread is (maybe if they all are paused)
  • Anonymous
    June 23, 2004
    I want to set up a remote Server for the specific purpose of being the development enviornment for serveral developers. When you terminal service into the server, VS.Net only allows one debugger to be running concurrently.