Date: Wed, 15 Feb 2006 15:31:03 -0500
From: Jeff Dike <jdike@addtoit.com>
To: "Charles P. Wright" <cwright@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ptrace and threads
Message-ID: <20060215203103.GA7634@ccure.user-mode-linux.org>
References: <1140030841.10553.9.camel@polarbear.fsl.cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1140030841.10553.9.camel@polarbear.fsl.cs.sunysb.edu>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 682
Lines: 16

On Wed, Feb 15, 2006 at 02:14:01PM -0500, Charles P. Wright wrote:
> I tried using
> ptrace(PTRACE_DETACH, ..., ..., SIGSTOP) in the original tracing process
> to stop the process after the fork, followed by a ptrace(PTRACE_ATTACH)
> in the new tracing process.

This has worked for me in the past.  The one tricky bit is that the process
needs a SIGCONT before it will run again (and appear to be active under
the new tracer).

				Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/