Linked by Thom Holwerda on Mon 6th Apr 2009 00:05 UTC
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.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2007-07-27
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-12
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