I do the same as Goran. I use gvim and cmake when working in Linux. I have some custom bash aliases setup for making greps easier, but other than that I use a linux console the vast majority of the time. I use ddd or kgdb for debugging. Valgrind (as was mentioned) is great for leak detection.

If I were going to use an IDE though in Linux I would probably use QtCreator or Code::Blocks.

I like Mecurial for source control. Wireshark is an excellent program for debugging network related stuff, but tcpdump can be useful also.

Just don't underestimate the power of a console... the ability to define aliases can be very powerful. Especially when you learn redirection operators. I also write tons of bash scripts to automate things.

I do the same as Goran. I use gvim and cmake when working in Linux. I have some custom bash aliases setup for making greps easier, but other than that I use a linux console the vast majority of the time. I use ddd or kgdb for debugging. Valgrind (as was mentioned) is great for leak detection.

If I were going to use an IDE though in Linux I would probably use QtCreator or Code::Blocks.

I like Mecurial for source control. Wireshark is an excellent program for debugging network related stuff, but tcpdump can be useful also.

Just don't underestimate the power of a console... the ability to define aliases can be very powerful. Especially when you learn redirection operators.