5 ms·

I personally don't use debugger that much but whenever I have used it, I have always been amazed at VS's debugger capability. I don't think I am exaggerating wh

I personally don't use debugger that much but whenever I have used it, I have always been amazed at VS's debugger capability. I don't think I am exaggerating when I say that VS has the best debugger across all languages/platforms. I think this is a GREAT news for all the developers.

stinos 11y ago
VS has the best debugger Yes and no :P Afaik gdb can for particular languages do everything the VS debugger can do, even more (or so I heard once), but the major and utterly important difference is the fact the VS debugger comes with the IDE and the 'I' in the word makes it so much easier to use than anything else out there that usually you can get a lot done with it in a much shorter timespan than with other debuggers. And as such gives people the right to call it the best debugger, imo.
- yoklov 11y ago
  Still takes a lot less time to use VS than to use the XCode debugger IMO. Having to expand anon struct/union members makes debugging in some codebases a real pain.
  - beached_whale 11y ago
    Not sure if available in XCode or GDB, but the ability to tell VS debugger how to display custom structures is very useful
omtose 11y ago
You cannot step back with VS's debugger, can you?
- WDCDev 11y ago
  You can. I just drag the arrow that appears on broken execution "upwards" to a previous line of code. There might be another way to do it.
  - Lawtonfogle 11y ago
    Does this undo previous commands or does it just rerun code?
    - to3m 11y ago
      Neither - it changes the program counter, ready for the next operation. It's not terribly cunning, but it's sometimes useful.
josteink 11y ago
> VS has the best debugger Not to nitpick or disregard the rest of your comment (VS has a really good debugger), but "best" always required qualifying. Best in what cases? Best in what way? There are times when the "best" debugger available without a doubt is WinDbg, with it being archaic, oldfashioned, command-line based, completely un-automated and all that fully accounted for. Why? Because I can copy the 500KB exe-file into a production environment, run it there and debug issues found nowhere else. And obviously you're not going to install VS on your production-server, and if you did, those builds are release-builds anyway, without debug-assistance or PDBs, so the VS-debugger would be handicapped anyway. So yeah. Just a slight nit-pick that "best" always has to be qualified.
- plorkyeran 11y ago
  VS can debug processes on remote machines with only a small helper process running on that machine, and while you shouldn't deploy PDBs onto your production servers, there's no reason not to generate them for your release builds.
  - josteink 11y ago
    > VS can debug processes on remote machines with only a small helper process running on that machine You first please :) I've tried doing that several times and always ended up giving up. If it's not firewalling, its UAC or cross domain trust issues, or DCOM configuration, or process permissions and probably 200 other things which has failed on me in the past. It only works in the most trivial of configurations. Back in the real world I've only been able to use it once or twice, non-repeatably.
    - plorkyeran 11y ago
      I've never had it be particularly difficult. It does generally require a VPN since forwarding DCOM over ssh is challenging.
  - deng 11y ago
    http://en.wikipedia.org/wiki/Gdbserver http://en.wikipedia.org/wiki/Gdbserver Visual Studio misses features like Python scripting, which for instance in gdb allows you to define pretty printers for your objects, which is immensely useful for complex data structures. The VS debugger also does not have a proper MI, at least I never heard of one. The only thing I miss from gdb is "edit and continue", which I admit is pretty cool.
green7ea 11y ago
I've seen this best debugger thing come up a few times before. I'm currently working with windows on a project right now and I'm finding the VS debugger more limited than GDB. With GDB I can create scripts which analyse and print complex memory layouts very quickly and efficiently. With valgrind, I can find memory leaks and other unwanted behaviors. With gcc's dump-tree family of options, I can see how my code is turned into assembly. I haven't been able to do these things well under VS and I think it comes down to preference and habit. So my question is, what makes VS's debugger the "best debugger", what am I missing?
- maxlybbert 11y ago
  Ease of use and discoverability. For people accustomed to IDEs, the fact that they don't have to remember "n" means "next," "s" means "step into," "info breakpoints" will say which breakpoints you've set, etc. is a big deal. Yes, you can use DDD for that, but frankly, it doesn't look as nice. Additionally, if you want to see what value a variable has, simply hover over it with the mouse pointer. This works for ints, but it also works for std::vector<std::map<int, std::string> >. You can get the same functionality in GDB, but it takes a little work to set it up.
- forgottenpass 11y ago
  So my question is, what makes VS's debugger the "best debugger", what am I missing? It's not (just) features, it's the interface to those features. The possibility cap may be lower for you, but that doesn't matter to people who just want an approachable interface to step through their code. This is the part where I'm an elitist asshole: There are developers that program by spending all day, every day in the debugger. They're almost never going to do anything fancy, they just want an easy way to fix their code. Command line gdb is too much effort to learn, and of the IDEs that hook into debuggers, VS does it the best.
  - tracker1 11y ago
    I have to agree here... When I've had to fall into using a debugger pragmatically VS integration is probably the best experience I've had (eclipse, intellij etc don't compare). That said, having been working a lot with node/iojs modules the past few years, I find that experience even better. I'm pretty sure others who are using scripted languages with a REPL can probably state the same. Running in an environment where you can jump in anywhere, call a particular script and replace variables for testing is a powerful experience. I don't mean to start a scripted vs. compiled war... they both have their place. Just mentioning because people will reach for a compiler for things that could be much simpler with a scripted environment more often than not.
vbcr 11y ago
I have debugged a C# application in VS and a Java application in IntelliJ and in Eclipse. I did not see any debugging features in VS that can claim its superiority over the others. May be I have not used all the features that were available. Are there any features in VS debugger that are better or non-existent in Java IDEs?
- mtVessel 11y ago
  I haven't used IntelliJ, but "Set Next Statement" was what I missed most using Eclipse.
  - ygra 11y ago
    IntelliJ doesn't seem to have it either, which is a pity. It happens quite often that I accidentally step over a line that does something I wanted to step into. In VS, if I know that that line doesn't have any bad side effects when executed twice, I can just pull the instruction pointer (the yellow arrow) back up and step into the line this time. Another thing I frequently miss in other debuggers is being able to place break-points on statements, not just lines, e.g. the individual parts in a for loop header.
- Locke1689 11y ago
  Unless you buy JRebel, VS supports a lot more Edit-and-Continue (JVM hot code swap) operations. I'm also not sure if you can execute Java 8 lambda expressions in the watch window while debugging.
rasur 11y ago
>I don't think I am exaggerating when I say that VS has the best debugger across all languages/platforms. Have you used any of the debuggers one finds in Smalltalk environments, out of interest? EDIT: typo

stinos 11y ago

VS has the best debugger Yes and no :P Afaik gdb can for particular languages do everything the VS debugger can do, even more (or so I heard once), but the major and utterly important difference is the fact the VS debugger comes with the IDE and the 'I' in the word makes it so much easier to use than anything else out there that usually you can get a lot done with it in a much shorter timespan than with other debuggers. And as such gives people the right to call it the best debugger, imo.

yoklov 11y ago
Still takes a lot less time to use VS than to use the XCode debugger IMO. Having to expand anon struct/union members makes debugging in some codebases a real pain.
- beached_whale 11y ago
  Not sure if available in XCode or GDB, but the ability to tell VS debugger how to display custom structures is very useful

omtose 11y ago

You cannot step back with VS's debugger, can you?

WDCDev 11y ago
You can. I just drag the arrow that appears on broken execution "upwards" to a previous line of code. There might be another way to do it.
- Lawtonfogle 11y ago
  Does this undo previous commands or does it just rerun code?
  - to3m 11y ago
    Neither - it changes the program counter, ready for the next operation. It's not terribly cunning, but it's sometimes useful.

josteink 11y ago

> VS has the best debugger Not to nitpick or disregard the rest of your comment (VS has a really good debugger), but "best" always required qualifying. Best in what cases? Best in what way? There are times when the "best" debugger available without a doubt is WinDbg, with it being archaic, oldfashioned, command-line based, completely un-automated and all that fully accounted for. Why? Because I can copy the 500KB exe-file into a production environment, run it there and debug issues found nowhere else. And obviously you're not going to install VS on your production-server, and if you did, those builds are release-builds anyway, without debug-assistance or PDBs, so the VS-debugger would be handicapped anyway. So yeah. Just a slight nit-pick that "best" always has to be qualified.

plorkyeran 11y ago
VS can debug processes on remote machines with only a small helper process running on that machine, and while you shouldn't deploy PDBs onto your production servers, there's no reason not to generate them for your release builds.
- josteink 11y ago
  > VS can debug processes on remote machines with only a small helper process running on that machine You first please :) I've tried doing that several times and always ended up giving up. If it's not firewalling, its UAC or cross domain trust issues, or DCOM configuration, or process permissions and probably 200 other things which has failed on me in the past. It only works in the most trivial of configurations. Back in the real world I've only been able to use it once or twice, non-repeatably.
  - plorkyeran 11y ago
    I've never had it be particularly difficult. It does generally require a VPN since forwarding DCOM over ssh is challenging.
- deng 11y ago
  http://en.wikipedia.org/wiki/Gdbserver http://en.wikipedia.org/wiki/Gdbserver Visual Studio misses features like Python scripting, which for instance in gdb allows you to define pretty printers for your objects, which is immensely useful for complex data structures. The VS debugger also does not have a proper MI, at least I never heard of one. The only thing I miss from gdb is "edit and continue", which I admit is pretty cool.

green7ea 11y ago

I've seen this best debugger thing come up a few times before. I'm currently working with windows on a project right now and I'm finding the VS debugger more limited than GDB. With GDB I can create scripts which analyse and print complex memory layouts very quickly and efficiently. With valgrind, I can find memory leaks and other unwanted behaviors. With gcc's dump-tree family of options, I can see how my code is turned into assembly. I haven't been able to do these things well under VS and I think it comes down to preference and habit. So my question is, what makes VS's debugger the "best debugger", what am I missing?

maxlybbert 11y ago
Ease of use and discoverability. For people accustomed to IDEs, the fact that they don't have to remember "n" means "next," "s" means "step into," "info breakpoints" will say which breakpoints you've set, etc. is a big deal. Yes, you can use DDD for that, but frankly, it doesn't look as nice. Additionally, if you want to see what value a variable has, simply hover over it with the mouse pointer. This works for ints, but it also works for std::vector<std::map<int, std::string> >. You can get the same functionality in GDB, but it takes a little work to set it up.
forgottenpass 11y ago
So my question is, what makes VS's debugger the "best debugger", what am I missing? It's not (just) features, it's the interface to those features. The possibility cap may be lower for you, but that doesn't matter to people who just want an approachable interface to step through their code. This is the part where I'm an elitist asshole: There are developers that program by spending all day, every day in the debugger. They're almost never going to do anything fancy, they just want an easy way to fix their code. Command line gdb is too much effort to learn, and of the IDEs that hook into debuggers, VS does it the best.
- tracker1 11y ago
  I have to agree here... When I've had to fall into using a debugger pragmatically VS integration is probably the best experience I've had (eclipse, intellij etc don't compare). That said, having been working a lot with node/iojs modules the past few years, I find that experience even better. I'm pretty sure others who are using scripted languages with a REPL can probably state the same. Running in an environment where you can jump in anywhere, call a particular script and replace variables for testing is a powerful experience. I don't mean to start a scripted vs. compiled war... they both have their place. Just mentioning because people will reach for a compiler for things that could be much simpler with a scripted environment more often than not.

vbcr 11y ago

I have debugged a C# application in VS and a Java application in IntelliJ and in Eclipse. I did not see any debugging features in VS that can claim its superiority over the others. May be I have not used all the features that were available. Are there any features in VS debugger that are better or non-existent in Java IDEs?

mtVessel 11y ago
I haven't used IntelliJ, but "Set Next Statement" was what I missed most using Eclipse.
- ygra 11y ago
  IntelliJ doesn't seem to have it either, which is a pity. It happens quite often that I accidentally step over a line that does something I wanted to step into. In VS, if I know that that line doesn't have any bad side effects when executed twice, I can just pull the instruction pointer (the yellow arrow) back up and step into the line this time. Another thing I frequently miss in other debuggers is being able to place break-points on statements, not just lines, e.g. the individual parts in a for loop header.
Locke1689 11y ago
Unless you buy JRebel, VS supports a lot more Edit-and-Continue (JVM hot code swap) operations. I'm also not sure if you can execute Java 8 lambda expressions in the watch window while debugging.

rasur 11y ago

>I don't think I am exaggerating when I say that VS has the best debugger across all languages/platforms. Have you used any of the debuggers one finds in Smalltalk environments, out of interest? EDIT: typo