truss issue

Don Lewis truckman at FreeBSD.org
Mon Dec 15 13:14:10 PST 2003


On 15 Dec, Doug White wrote:

> My reading of it is that it is truss hitting itself with the same signal
> that killed the process that it was tracing so that truss will exit
> showing that it was killed by a signal. So this is actually implementing
> the requested functionality.  Processes that exit due to a signal don't
> return an exit code.  It seems keyed on 'sigexit' whatever that is.

Hmn, I wonder if it would be cleaner to exec() the executable to be
traced in the parent process and run truss in the child ...


More information about the freebsd-current mailing list