Hi, On Fri, Sep 12, 2008 at 10:24 AM, Andrej van der Zee <[EMAIL PROTECTED]> wrote: > Hi, > >> I don't understand your problem here. If you're ptrace'ing a process, >> and that process >> spawns a new process/thread, you can get this event notification >> through ptrace() and >> attach to the newly cloned task. Why do you think you need to alter >> the place where >> the thread is spawned? > > I have a root-process that spawns threads that I want to monitor. To be able > to ptrace() all its threads (and the threads descendant threads/processes) > in the way you suggest, I need another process to monitor the root-process. > That I can't do, I just want to monitor the treads and follow > forks/exec/create_thread etc. It's a pity that ptrace() needs a parent > process to monitor a child, and it can't trace itself from within a > thread/process. > This limitation from ptrace is normal. It was designed for debugging not monitoring. As you can understand, you never debug yourself.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
