Linked by Thom Holwerda on Thu 2nd May 2013 10:15 UTC
BeOS & Derivatives "In the past few weeks, I've managed to find a bit more free time to work on Haiku. As per usual, the lion's share of this time was spent on improving our integrated debugger. As such, I thought I'd give a brief overview of what's been added, and how it can be useful."
Thread beginning with comment 560353
To read all comments associated with this story, please click here.
X11 "gui" debugger for C/C++/etc - "ups"
by userw014 on Thu 2nd May 2013 20:24 UTC
userw014
Member since:
2010-11-05

I used 'ups" to work on a debugging network daemons (in particular, Merit Computer Network's RADIUS server, based on the Livingston code). It offered a very nice way to view the code and step through it, etc. as you would expect a debugger to do, and to hold various various variables (including structures) in view at the same time.

Since I haven't done C/C++ coding on that scale (several hundred thousand lines of code) for network daemons for some time, I've been satisfied with "gdb" when I need to.

Most of my coding since then has been without the aid of debugging tools since it's involved scripted languages from web servers, cron jobs, etc. where I can't attach a debugger and have to suffer with the equivalent of scattering "printf" statements through the code, guarded by a "debug_level" variable. (Sad and tedious.) I miss "ups".

Reply Score: 2

acobar Member since:
2005-11-15

Most of my coding since then has been without the aid of debugging tools since it's involved scripted languages from web servers, cron jobs, etc. where I can't attach a debugger ...


Actually, you can, but, as with all regular debugging, you will need a cup of coffee to bear the slowness of the process. If you use bash, there is bashdb. From the same author there is a debugger for perl and links on bashdb site to a ruby debugger. PHP has some debuggers as also Python so, actually, there is a chance you will be served by a debugger for your language of choice.

Regardless, I find it really handy to have "print/echo" macros on the critical parts of my code, no matter what was used. As developers, most of the times we have a good insight on where things can go wrong and start to wreak havoc. For me it is usually faster this way to spot, or at least narrow the boundaries of, where things got crazy.

Reply Parent Score: 3