From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79143 invoked by alias); 3 Feb 2017 16:21:55 -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 79110 invoked by uid 89); 3 Feb 2017 16:21:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Deletes, Starts, H*MI:sk:2016112 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 ESMTP; Fri, 03 Feb 2017 16:21:53 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CA12B7E9DA; Fri, 3 Feb 2017 16:21:53 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v13GLgeW023370; Fri, 3 Feb 2017 11:21:43 -0500 Subject: Re: [PATCH 2/2] Avoid step-over infinite loop in GDBServer To: Antoine Tremblay , gdb-patches@sourceware.org References: <20161129120702.9490-1-antoine.tremblay@ericsson.com> <20161129120702.9490-2-antoine.tremblay@ericsson.com> From: Pedro Alves Message-ID: <353b676b-5f13-6983-d25e-d07e49f89182@redhat.com> Date: Fri, 03 Feb 2017 16:21:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161129120702.9490-2-antoine.tremblay@ericsson.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-02/txt/msg00098.txt.bz2 On 11/29/2016 12:07 PM, Antoine Tremblay wrote: > - GDBServer stops on instruction A in thread 1. > - Deletes thread 1 single-step breakpoint. > - Starts a step-over of thread 1 to step-over the thread 2 breakpoint. > - GDBServer finishes a step-over and is at instruction B. > - GDBserver starts a step-over of thread 1 to step-over the thread 3 > breakpoint at instruction B. > - GDBServer stops on instuction A in thread 1. > - GDBServer is now in an infinite loop. This sounds to me very much like a fairness issue. There were three threads stopped that needed to move past a breakpoint, but gdbserver always picks thread 1. Why? Thanks, Pedro Alves