Re: strace only one child process

phil-news-nospam@xxxxxxxx wrote:
On 21 Oct 2006 03:35:52 -0700 tmp123 <tmp123@xxxxxxxxx> wrote:

| About modify "strace", it is a posibility. I should evaluate the
| necessary effort. The idea will be add to the "-f" option an optional
| numerical argument: maximum number of childs to follow.

I would suggest integrating it with the -e option, allowing _any_ kind
of specifiable event to be counted to determine when to stop tracing
that event or to stop strace altogether. Then while you would be using
it to count a maximum of fork() calls, someone else might find value in
stopping tracing after some number of open() calls.



Yes, is true. A program like "truss" allows 3 lists of independent
events: the ones to trace, the ones to start the trace and the ones to
end it.

I'm wondering why "strace" does not have it.

Kind regards.

.

Relevant Pages

  • Profiling ftw?
    ... The stuff here is a brain dump; there's stuff about ptrace and strace ... Trace and track processes separately, ... Report on library calls ... It also won't trace calls to dlopened libraries. ...
    (Ubuntu)
  • Re: unable to generate form in isql
    ... Pity HP-UX does not have truss or strace or any supported way of ... Download tusc and trace the process. ...
    (comp.databases.informix)
  • Re: tracing through C function calls
    ... Shashank Khanvilkar wrote: ... > I have read on previos posts about ptrace, strace, gprof and truss.. ... pages and see you can easily trace child process's system calls. ...
    (comp.unix.programmer)
  • Re: CEPTCL: Doesnt RX multicast, has anyone seen it work before?
    ... the tcludp process... ... If you don't want me to trace the wish, ... You managed to get a strace output from the CEP Tcl package, ...
    (comp.lang.tcl)
  • Re: How to trace a process with ptrace when it forks a new process ?
    ... to trace its child too, if the process forks a child, ... The code of strace is quite complex because it supports so many different systems. ... But I don't want to do it in this way because I don't need to trace every system call. ... What I need to trace is when the process forks a new process and exits. ...
    (comp.os.linux.development.system)