From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, Pedro Alves <pedro@palves.net>,
gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Fix warning in foreach_arch selftests
Date: Thu, 2 Jun 2022 13:44:09 -0400 [thread overview]
Message-ID: <ac81790c-d64f-16b2-8787-e108b2af75ed@simark.ca> (raw)
In-Reply-To: <59e73c8e-2ba5-c980-3369-02c3e53be21d@suse.de>
On 6/2/22 11:44, Tom de Vries via Gdb-patches wrote:
> On 6/1/22 21:08, Simon Marchi wrote:
>> Hi Tom,
>>
>> This introduces some failures for me:
>>
>> Running selftest print_one_insn::A6.^M
>> Self test failed: Cannot access memory at address 0x0^M
>
> Hi Simon,
>
> sorry for not catching this, I forgot to test with --enable-targets=all, I'll try to fix the default in my build scripts.
>
> I've done a new version of the existing patch (so it applies once the old one is reverted).
>
> Mainly because I realized that there's an easier way to handle the osabi none setting:
> ...
> @@ -68,6 +68,7 @@ foreach_arch_test_generator (const std::string &name,
> {
> struct gdbarch_info info;
> info.bfd_arch_info = bfd_scan_arch (arch);
> + info.osabi = GDB_OSABI_NONE;
> struct gdbarch *gdbarch = gdbarch_find_by_info (info);
> SELF_CHECK (gdbarch != NULL);
> function (gdbarch);
> ...
>
> Currently regression testing, but at least fixes the ARC regression.
It fixes the gdb.gdb/unittest.exp failure, but introduces:
FAIL: gdb.arch/amd64-osabi.exp: arch=i386:x86-64: print sizeof (void*)
FAIL: gdb.arch/amd64-osabi.exp: arch=i386:x86-64: print sizeof (long double)
FAIL: gdb.arch/amd64-osabi.exp: arch=i386:x64-32: print sizeof (long double)
Simon
next prev parent reply other threads:[~2022-06-02 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 10:41 Tom de Vries via Gdb-patches
2022-06-01 14:32 ` Pedro Alves
2022-06-01 16:36 ` Tom de Vries via Gdb-patches
2022-06-01 17:10 ` Pedro Alves
2022-06-01 19:08 ` Simon Marchi via Gdb-patches
2022-06-02 15:44 ` Tom de Vries via Gdb-patches
2022-06-02 17:44 ` Simon Marchi via Gdb-patches [this message]
2022-06-02 18:35 ` Tom de Vries via Gdb-patches
2022-06-04 7:23 ` Tom de Vries via Gdb-patches
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=ac81790c-d64f-16b2-8787-e108b2af75ed@simark.ca \
--to=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
/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