From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32094 invoked by alias); 12 Dec 2008 23:22:23 -0000 Received: (qmail 32086 invoked by uid 22791); 12 Dec 2008 23:22:23 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Dec 2008 23:21:40 +0000 Received: from zps35.corp.google.com (zps35.corp.google.com [172.25.146.35]) by smtp-out.google.com with ESMTP id mBCNLc9x011807 for ; Fri, 12 Dec 2008 15:21:38 -0800 Received: from rn-out-0910.google.com (rnw45.prod.google.com [10.38.23.45]) by zps35.corp.google.com with ESMTP id mBCNLbGf001626 for ; Fri, 12 Dec 2008 15:21:37 -0800 Received: by rn-out-0910.google.com with SMTP id 45so1614903rnw.14 for ; Fri, 12 Dec 2008 15:21:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.33.15 with SMTP id g15mr2199991agg.54.1229124096844; Fri, 12 Dec 2008 15:21:36 -0800 (PST) In-Reply-To: <20081212231626.GA15292@caradoc.them.org> References: <20081212211315.57CE01C7A79@localhost> <20081212212838.GA8833@caradoc.them.org> <20081212231626.GA15292@caradoc.them.org> Date: Fri, 12 Dec 2008 23:22:00 -0000 Message-ID: Subject: Re: gdbserver ptrace not doing waitpid after attaching to threads? From: Doug Evans To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00048.txt.bz2 On Fri, Dec 12, 2008 at 3:16 PM, Daniel Jacobowitz wrote: >> 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. Right, new threads could be created after the SETOPTIONS goes into affect. But I'm still unclear whether SETOPTIONS will deliver threads that have already been created and exist when gdbserver attaches.