Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Open Sourcing Visual Studio’s GDB/LLDB Debug Engine

blogs.msdn.com

Post reply on HN
Print view View original

41–42 of 42 posts

Re: Open Sourcing Visual Studio’s GDB/LLDB Debug Engine

#41

Post by orionblastar »

I miss the days of MASM and Codeview. I used to debug DOS programs in Codeview and could step into and out of code lines and even modify the code. By changing a JE to JNE I was able to bypass the Lotus 123 2.0 protection so it could be installed on a Netware drive instead of just a floppy disk.

GDB/LLDB it is good that Microsoft is open sourcing their debug tools. Microsoft has been struggling with improving Visual Studio and Dotnet, so in open sourcing them or parts of them in CoreCLR, Visual Studio Core, and then GDB/LLDB they are letting open source developers participate in improving them.

Sure it isn't the full version of Visual Studio, I don't expect Microsoft to give away everything but small parts of it. Sometimes less is more, in that the fewer lines of code the smaller the program the faster it runs.

I would like to see an Office Core and SQL Server Core as well if they can.

Re: Open Sourcing Visual Studio’s GDB/LLDB Debug Engine

#42

Post by HanyouHottie »

tracker1 wrote: post #37
forgottenpass wrote: post #20

Earlier quoted context omitted.

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.…

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 wher…

Your language doesn't need to be interpreted to have a REPL. Haskell has a REPL. The Immediate window in Visual Studio is essentially a REPL for all .NET languages (so you get that and the VS debugger together, win/win).
Post reply on HN