On Wed, May 19, 2010 at 4:51 PM, Alfred Perlstein wrote:
> * Dan McNulty [100519 07:13] wrote:
>> Thanks for all the great suggestions!
>>
>> It looks like the kevent system call is the closest to what I need.
>> However, I didn't mention this, but I would like the process being
>> traced to be s
* Dan McNulty [100519 07:13] wrote:
> Thanks for all the great suggestions!
>
> It looks like the kevent system call is the closest to what I need.
> However, I didn't mention this, but I would like the process being
> traced to be stopped on entrance to fork, exec, etc. This would be
> similar t
Thanks for all the great suggestions!
It looks like the kevent system call is the closest to what I need.
However, I didn't mention this, but I would like the process being
traced to be stopped on entrance to fork, exec, etc. This would be
similar to Linux's ptrace interface which sends a SIGTRAP
* Dan McNulty [100517 08:02] wrote:
> Hi all,
>
> I have been experimenting with ptrace to determine when a child
> process forks or calls exec. Particularly, I have explored tracing
> every system call entry and exit similar to what the truss utility
> does, and for my case, the performance impa
- Original Message
> From: Dan McNulty
> To: freebsd-hackers@freebsd.org
> Sent: Mon, May 17, 2010 11:33:31 AM
> Subject: Efficient way to determine when a child process forks or calls exec
>
> Hi all,
>I have been experimenting with ptrace to determine when a
> child process forks
On 05/17/2010 10:33, Dan McNulty wrote:
> Hi all,
>
> I have been experimenting with ptrace to determine when a child
> process forks or calls exec. Particularly, I have explored tracing
> every system call entry and exit similar to what the truss utility
> does, and for my case, the performance i
6 matches
Mail list logo