From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28708 invoked by alias); 12 Dec 2008 23:17:11 -0000 Received: (qmail 28698 invoked by uid 22791); 12 Dec 2008 23:17:11 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Dec 2008 23:16:29 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 639E51053D; Fri, 12 Dec 2008 23:16:27 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 42AD510499; Fri, 12 Dec 2008 23:16:27 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LBHFC-00041N-Si; Fri, 12 Dec 2008 18:16:26 -0500 Date: Fri, 12 Dec 2008 23:17:00 -0000 From: Daniel Jacobowitz To: Doug Evans Cc: gdb@sourceware.org Subject: Re: gdbserver ptrace not doing waitpid after attaching to threads? Message-ID: <20081212231626.GA15292@caradoc.them.org> Mail-Followup-To: Doug Evans , gdb@sourceware.org References: <20081212211315.57CE01C7A79@localhost> <20081212212838.GA8833@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-12/txt/msg00047.txt.bz2 On Fri, Dec 12, 2008 at 03:06:44PM -0800, Doug Evans wrote: > I mightn't have been clear enough btw. I'm observing these things > from doing an attach in gdb. Example below. Oh! Well then. Sounds like it's gotten broken. I know we've fixed this at least once before. > This is the first attach that gdbserver does, the one for the process. > Might it be possible that one has to wait for SIGSTOP even before > ptrace (SETOPTIONS)? :-) Yes, that's correct. A bit silly, but correct. > For clarification, your comment: > > > It shouldn't be > > doing any ATTACH; instead it should be trusting SETOPTIONS to deliver > > new threads to it via wait. > > was for the case where gdbserver starts the program, and not for the > case where gdbserver attaches to the program, right? Well, it's for any thread created once the program is running under gdbserver control. Which amounts to the same thing here. -- Daniel Jacobowitz CodeSourcery