Live data from Hacker News

Building and modifying Linux Kernel with Visual Studio

sysprogs.com

21–30 of 38 posts

Re: Building and modifying Linux Kernel with Visual Studio

#21
post #7

Earlier quoted context omitted.

Because the Visual Studio debugger is the most advanced, wonderful, and beautiful (if that's a thing) debugger ever written.

Just step back and think for a minute why that is the case.

Because writing good debuggers is unglamorous hard work.

Actually, I think the VS C++ debugger is only decent - not great, just decent. I prefer the Borland debugger kernel, seen these days in Embarcadero Delphi and C++ Builder, the CPU view in particular. Although if you're working with mixed native and .NET code, it's quite good.

VS's ability to comprehend C++ code and provide meaningful code completion, follow symbol references, etc. even when it isn't able to compile the C++ is excellent, however.

Re: Building and modifying Linux Kernel with Visual Studio

#22
post #7

Earlier quoted context omitted.

Just step back and think for a minute why that is the case.

Is it because Microsoft has always invested heavily in development tools to encourage development of Windows software?

I don't think that's the case when VS bundle is priced in thousands of dollars. They just want to make good product.

Re: Building and modifying Linux Kernel with Visual Studio

#23
post #16

Why?

That's a great question. Here's my take on it: I switched from Windows to Linux over a decade ago...but as somebody that has to often write a lot of C/C++ code, man do I miss Visual C++. I've gone through all the IDEs (Eclipse, Code::Blocks, Anjuta, QtCreator, etc). QtCreator comes close for me, but I feel most comfortable with Sublime Text and a terminal for compiling/debugging/profiling. Visual C++'s intellisense a…

I don't suppose you've heard of KDevelop?

Re: Building and modifying Linux Kernel with Visual Studio

#26
post #3

No, just no! Stop this madness!

Lol, i imagined Stallman saying this

I have to admit - when I first saw this I heard that record scratch sound and the universe stopped for a moment.

Technically-speaking, this is pretty cool thing. Socially, this is so wrong on so many levels, I'm surprised no one has done it before.

We could probably power a small city with the electricity generated by future-Stallman spinning in his grave over this.

Though, we also have to allow that he might become zombie-Stallman.

Re: Building and modifying Linux Kernel with Visual Studio

#27
post #16

Why?

That's a great question. Here's my take on it: I switched from Windows to Linux over a decade ago...but as somebody that has to often write a lot of C/C++ code, man do I miss Visual C++. I've gone through all the IDEs (Eclipse, Code::Blocks, Anjuta, QtCreator, etc). QtCreator comes close for me, but I feel most comfortable with Sublime Text and a terminal for compiling/debugging/profiling. Visual C++'s intellisense a…

Have you heard of JetBrains' C++ IDE? http://blog.jetbrains.com/objc/2014/02/jetbrains-c-ide-statu...

Re: Building and modifying Linux Kernel with Visual Studio

#28

Earlier quoted context omitted.

Because the Visual Studio debugger is the most advanced, wonderful, and beautiful (if that's a thing) debugger ever written.

It has a steep learning curve, but the package Microsoft calls "debugging tools for windows" (windbg, cdb, kd) really puts the VS debugger to shame, to the point where I am frustrated when I try to use it. If you want to point and click your way through variables I guess VS is OK, but if you want everything you might ever want to know about a process it is frustrating.

You can use the WinDbg debugging engine as your debugging engine in Visual Studio, which allows you to combine the benefits of the IDE with the power of WinDbg virtually seamlessly.

Re: Building and modifying Linux Kernel with Visual Studio

#30
post #20
post #11

Earlier quoted context omitted.

I keep my code portable to Windows soley for the purpose of getting to use the Visual Studio debugger. Likewise, Windows developers should write portable code so they can use valgrind.

No need for valgrind when using memory safe languages :)

Are your memory safe languages also concurrency/data-race safe? (<3 valgrind DRD)
Post reply on HN