From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PING][RFC][gdb] Add maint set skip-prologue
Date: Wed, 7 Sep 2022 19:18:52 +0200 [thread overview]
Message-ID: <5fe179c8-52c4-0dd4-7d25-9dfce75d782b@suse.de> (raw)
In-Reply-To: <23a54469-9ec2-eec7-4937-d0cac5b1e687@suse.de>
On 9/7/22 12:04, Tom de Vries wrote:
> On 9/7/22 11:33, Tom de Vries via Gdb-patches wrote:
>> On 8/10/22 15:48, Tom de Vries via Gdb-patches wrote:
>>> and fix a few other test-cases by
>>> specifying the breakpoint location in a way that's independent from the
>>> prologue.
>>>
>>> gdb/testsuite/gdb.ada/access_tagged_param.exp | 2 +-
>>> gdb/testsuite/gdb.ada/ptype_tagged_param.exp | 2 +-
>>> gdb/testsuite/gdb.ada/ref_param.exp | 2 +-
>>
>> I've committed this separately at
>> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=154f2735ad4c2eb0985086b113825e6f4f3abcf1
>
>
> Ping, and resubmit with update patch.
And, FTR, this fixes the last two FAILs I see with openSUSE Leap 15.4
aarch64.
Thanks,
- Tom
prev parent reply other threads:[~2022-09-07 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 13:48 [RFC][gdb] " Tom de Vries
2022-09-07 9:33 ` Tom de Vries
2022-09-07 10:04 ` [PING][RFC][gdb] " Tom de Vries
2022-09-07 17:18 ` Tom de Vries [this message]
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=5fe179c8-52c4-0dd4-7d25-9dfce75d782b@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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).