From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128945 invoked by alias); 12 Feb 2016 20:15:29 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 128934 invoked by uid 89); 12 Feb 2016 20:15:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 12 Feb 2016 20:15:27 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id AB415C0B60F1; Fri, 12 Feb 2016 20:15:26 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u1CKFPjJ016339; Fri, 12 Feb 2016 15:15:25 -0500 Message-ID: <56BE3D5C.1060108@redhat.com> Date: Fri, 12 Feb 2016 20:15:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Don Breazeal , gdb-patches@sourceware.org Subject: Re: [PATCH v2 1/3] PR remote/19496, internal err forking-threads-plus-bkpt References: <1455150383-12456-1-git-send-email-donb@codesourcery.com> In-Reply-To: <1455150383-12456-1-git-send-email-donb@codesourcery.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-02/txt/msg00435.txt.bz2 Hi Don, On 02/11/2016 12:26 AM, Don Breazeal wrote: > On 2/1/2016 12:38 PM, Pedro Alves wrote: >> So the fork event has been reported out of target_wait but it was >> left pending on the infrun side (infrun.c:save_waitstatus) >> >> IOW, the fork event hasn't been processed by handle_inferior_event >> yet, so it hasn't made it to tp->pending_follow yet. >> >> The information is not lost, we're just looking for it in the >> wrong place. I think this would be the right fix: > > The fix below is essentially unchanged from your suggested fix. The commit > message has been updated for the new fix. > > Tested on Nios II Linux target with x86 Linux host, and native x86_64 Linux. OK. Fine for 7.11 as well. I'll need a bit more to think over patches 2 and 3. Thanks, Pedro Alves