But I don't want to look at the source code!

Sometimes quick and dirty get the job done. As Perl programmers say "There
is more than one way to do it" and in the case of a finding out why a
program is not doing what you would like to do this is very true. One could
fire up the debugger and dig into the source code but often simpler and
faster methods are available. In the cases where you don't have the source
code these may be all you have. t

Here I will present a certainly incomplete but what I have found to be an
invaluable list of commands and techniques for trouble shooting software of
all kinds under Linux. On other platforms you will find similar commands so
these techniques need not be limited to Linux.

LUG-talk-Oct-09.tar_.gz4.71 KB
Syndicate content Syndicate content