From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-46690-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 10142 invoked by alias); 6 Nov 2018 00:24:50 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 9861 invoked by uid 89); 6 Nov 2018 00:24:28 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:sk:gdb@sou, fd8, fd0, resume
X-HELO: mail-vs1-f54.google.com
Received: from mail-vs1-f54.google.com (HELO mail-vs1-f54.google.com) (209.85.217.54) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 06 Nov 2018 00:24:24 +0000
Received: by mail-vs1-f54.google.com with SMTP id s9so6282737vsk.7        for <gdb@sourceware.org>; Mon, 05 Nov 2018 16:24:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;        bh=moZHqi0MHBHZx/3WnJTK7QmuUlVFPDtlZZrHLQFxBXg=;        b=MxH/h7OPlLqhK8s9Fak/fmuHGeou/XN/9Iqz4KjYYhZcdl6XbbvlCZDqWj2aKjL+Bi         IKUvrTXVmHdr/3TV1RZ8jtlY1Ib7+gphiHpT9z7fRz6Dzpkb4Ee881IbsflgZRM5Nq/u         iYY3/87gZi92Tf3QHvvOOsMKnW5pc3RZOjij97sJTcDyUm/pnKdyUvB56kp6ejmDd0Ft         BN4IPdIbSw06zms29FmFA0DyWVhugZL9i6y9hEaN4dB4IKaKh+AyUx+j4Hb0nFASNrgx         l+DDsc3k4EpPPxXvXCTULpHGaUaBN+bYK+wmq2ANyMuSN4Hw56lyB7T/Zq8gHyvZicfL         pi1A==
MIME-Version: 1.0
References: <CAM4wpo-8gifqniHu7wNWsRRMZPdaBb1Msa=Wkt9BAMr6F=1fiQ@mail.gmail.com>
In-Reply-To: <CAM4wpo-8gifqniHu7wNWsRRMZPdaBb1Msa=Wkt9BAMr6F=1fiQ@mail.gmail.com>
From: Bill Morgan <arthurwilliammorgan@gmail.com>
Date: Tue, 06 Nov 2018 00:24:00 -0000
Message-ID: <CAM4wpo-r7R8SkqUsK0uAMxsKm=vKzk6kt-dqQE+ku6dF49fS_g@mail.gmail.com>
Subject: Re: arm remote step using software breakpoints doesn't finish the step
To: gdb@sourceware.org
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2018-11/txt/msg00001.txt.bz2

On Mon, Nov 5, 2018 at 11:42 AM Bill Morgan <arthurwilliammorgan@gmail.com>
wrote:

> For some reason GDB is setting breakpoints in an order that is causing a
> step to never finish.
>
> It sets a breakpoint at 0x22637fd0, then that breakpoint is hit, then sets
> one at 0x22637fd4, then that one is hit, then it puts one back at
> 0x22637fd0 again and the remote code runs until it loops back into this
> function again and fd0 is hit again, then sets bp at 0x22637fd4 again,
> etc., so the result is that the step never finishes.
>
> I'm wondering why it didn't set one at fd8.
>
> Any ideas?
>

I found an issue in my remote stub. I had multiple threads in the address
space with the breakpoint.

Thread 0x1f was current, but 0x1e was resuming first and hitting the
stepping breakpoint, so GDB kept trying to get 0x1f to hit the breakpoint
for the step.

I changed to always resume the current thread first so it has a chance to
hit the stepping breakpoint.