Linked by Thom Holwerda on Mon 6th Apr 2009 00:05 UTC
General Unix Take a look at some systems that enable you to trace the execution of applications and work out what they are doing without having to make any modifications to the source code, and even without having to stop and restart the application. See how with tracing alone, you can find and diagnose problems with just a few commands.
Thread beginning with comment 357345
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: DTrace superior.
by rcsteiner on Mon 6th Apr 2009 16:37 UTC in reply to "DTrace superior."
Member since:

It isn't that hard to create your own logging facility and trigger various stages of logging detail by sending signals to the running process.

We do that all the time with real-time message processing applications. Most of the time they log minimal information unless we're doing active troubleshooting, and then I can dump the world. :-)

No special debugger or external software required. Just a logging routine, tail, and more (or grep for searching).

Of course, we're only running dozens of trans/second max. Then again, we have four discrete levels of logging detail not including OFF, and it wouldn't be too hard to change things.

Edited 2009-04-06 16:40 UTC

Reply Parent Score: 2

RE[2]: DTrace superior.
by Kebabbert on Tue 7th Apr 2009 09:47 in reply to "RE: DTrace superior."
Kebabbert Member since:

Wouldnt it be easier if you tried DTrace on your application? There are several OSes with DTrace that you can run your application on.

Reply Parent Score: 2