On 27/10/10 23:03, Amos Shapira wrote:
On 28 October 2010 06:23, Shachar Shemesh wrote:
Same flags to clone in both cases (vi sets the same flags, and both strace
and fakeroot-ng change them to the same different flags).
I'm not aware of any settings that globally affects wait's behavior.
On 28 October 2010 06:23, Shachar Shemesh wrote:
> Same flags to clone in both cases (vi sets the same flags, and both strace
> and fakeroot-ng change them to the same different flags).
> I'm not aware of any settings that globally affects wait's behavior.
SIGCHLD? (not global, but part of the "e
On 27/10/10 20:53, Valery Reznic wrote:
OK, you was warned :)
Yes, I was. Still
How can two programs do the same thing on the same system,
and yet get such different results?
Let's take 'read' syscall.
read(10, )
I am not talking about a single syscall that behaves diffe
--- On Wed, 10/27/10, Shachar Shemesh wrote:
> From: Shachar Shemesh
> Subject: ptrace problem - confounded, dazed and confused at the
> inconsistencies
> To: "linux-il"
> Date: Wednesday, October 27, 2010, 2:07 PM
> Hi all,
Hi, Shachar.
>
> I know tha
On Wed, Oct 27, 2010 at 2:07 PM, Shachar Shemesh wrote:
>
> For threads, there is a strange set of events taking place. Both for strace
> and for fakeroot-ng, the clone system call gets modified. For both, the new
> thread created has the same debugger as the parent. For strace, the debugger
> run
Hi all,
I know that so much as types "man ptrace" is stepping into uncharted
territory, that I should abandon hope all ye' who enter here, etc.
Background - I am maintainer and author of an open source program called
"fakeroot-ng"[1]. This program uses the ptrace interface in order to
fool p
