Program Snapshot

[burns]

On Sat, 2003-09-20 at 19:44, Ben Duncan wrote:
> Unfortunately, the program was not compiled with debug, so that
> is out of the question.
> 
> What I am wanting to do, is like the OLD <Gasp> debug program
> that was in MS-DOS, where you could step thru and OR see the
> ASM code.
> 
> I am wanting to follow what the program is doing, and it is a
> "foreign" binary (Coff), so it has to be running.
> 

Sigh... per my (much) earlier post, please check out 'man strace'

Following are excerpts from the man intro:

"It  intercepts  and records the system calls which are called by a
process and the signals which are received by a process.  The name of
each system call, its arguments and its return value are printed on
standard error or to the file specified with the -o
option."                                                                                                                   
"...a close examination of this boundary is very useful for  bug
isolation, sanity checking and attempting to capture race conditions."
                                                                                                                             "Each  line  in the trace contains the system call name, followed by its
arguments in parentheses and its return value."

If a program fails, strace shows the point at which it failed and the
process involved.

-- 
burns