From: Adrian Oltean <adrian.oltean@nxp.com>
To: Luis Machado <luis.machado@arm.com>,
Keith Seitz <keiths@redhat.com>, John Baldwin <jhb@FreeBSD.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: [EXT] Re: Context switch during stepping causes weird behavior
Date: Thu, 13 Oct 2022 06:41:15 +0000 [thread overview]
Message-ID: <AM0PR04MB4628B0B4F89679D7B391E344F1259@AM0PR04MB4628.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <b564da74-fd57-61e3-6a4a-860a454b4026@arm.com>
Hi Luis,
Thank you for clarifying this. I concluded that displaced stepping is off
based on the description I found in the GDB user guide. Maybe it's worth
updating the docs as well.
Adrian
> -----Original Message-----
>
> On 10/12/22 07:46, Adrian Oltean via Gdb wrote:
> > Thanks guys. Looks like displaced stepping is off by default when GDB
> > is running in all-stop mode - my case. So I'll have to look for other
> > ways to work around the behavior I described.
>
> That is a bit misleading. It used to be the case it was only used for non-stop
> mode, but nowadays it is supported if the underlying target supports it.
>
> I don't think Arm (As in arm-none-elf, I'm assuming this is the case here) supports
> it, but when debugging linux-hosted Arm binaries, then it is supported.
>
> See gdb/infrun.c:gdbarch_supports_displaced_stepping.
> >
> > Adrian
> >
> >> Caution: EXT Email
> >>
> >> On 10/5/22 09:53, John Baldwin wrote:
> >>
> >>> I don't know off the top of my head if there is a knob to disable
> >>> displaced stepping.
> >> FYI:
> >>
> >> (gdb) apropos displaced
> >> set debug displaced -- Set displaced stepping debugging.
> >> set displaced-stepping -- Set debugger's willingness to use displaced stepping.
> >> show debug displaced -- Show displaced stepping debugging.
> >> show displaced-stepping -- Show debugger's willingness to use
> >> displaced stepping.
> >>
> >> Keith
> >
next prev parent reply other threads:[~2022-10-13 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 12:19 Adrian Oltean
2022-10-04 16:57 ` John Baldwin
2022-10-05 6:48 ` Adrian Oltean
2022-10-05 16:53 ` John Baldwin
2022-10-07 15:40 ` Keith Seitz
2022-10-12 6:46 ` [EXT] " Adrian Oltean
2022-10-13 6:34 ` Luis Machado
2022-10-13 6:41 ` Adrian Oltean [this message]
2022-10-10 9:52 ` Luis Machado
2022-10-12 6:40 ` [EXT] " Adrian Oltean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM0PR04MB4628B0B4F89679D7B391E344F1259@AM0PR04MB4628.eurprd04.prod.outlook.com \
--to=adrian.oltean@nxp.com \
--cc=gdb@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=keiths@redhat.com \
--cc=luis.machado@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).