Feature requests: list of PIDS, and all threads

[Denys Vlasenko]

On 03/09/2012 04:38 PM, George Spelvin wrote:
>> execve takes down entire multi-threaded program, thus what you propose
>> does not make sense: after execve in any thread, your multi-threaded
>> program won't be there anymore.
>>
>> Did you mean "track thread creation (clone), but not process creation
>> ([v]fork that is)"?
>
> I see how what I said was confusing, but I meant drop-on-exec;
> when debugging a particular program binary, the goal is to see
> all system calls made by that binary.  Which means tracing across
> the vfork to see what parameters are passed to execve, but once
> you change to a different text image, *then* is a good time
> to drop it.
>
> When debugging, execve() is a choke point for information transfer;
> it's usually easy to run the target program from the shell if it's
> misbehaving.

This makes sense.
When I tried to implement it, I noticed that "strace -o FILE -ff"
logging is horribly broken for our threaded_execve
test case, so I was working on fixing that first...

-- 
vda