From: Pedro Alves <pedro@palves.net>
To: Luis Machado <luis.machado@arm.com>,
Andrew Burgess <aburgess@redhat.com>,
John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 5/5] gdb: native target invalid architecture detection
Date: Wed, 8 Jun 2022 11:12:20 +0100 [thread overview]
Message-ID: <22be6164-79d7-c0f7-1b1b-c633be452e81@palves.net> (raw)
In-Reply-To: <9c711ccb-a558-8225-524b-5a1fa93fcee9@arm.com>
On 2022-06-08 08:54, Luis Machado wrote:
> On 6/7/22 19:42, Pedro Alves wrote:
>> On 2022-06-07 12:03, Luis Machado via Gdb-patches wrote:
>>
>>> Yeah, sorry for the poor experience. I can confirm your procedure is
>>> correct, and that you built GDB correctly. Unfortunately this part of
>>> the AArch64 port seems to have rotted away given it is a less common
>>> execution scenario.
>>
>> This is actually covered by the testsuite, since:
>>
>> ~~~~~
>> commit 71be1fdc3655a170f4b14d795e5c9e81fcea06ef
>> Author: Yao Qi <yao.qi@linaro.org>
>> AuthorDate: Tue Jul 7 16:58:19 2015 +0100
>> Commit: Yao Qi <yao.qi@linaro.org>
>> CommitDate: Tue Jul 7 16:58:19 2015 +0100
>>
>> Adjust gdb.multi tests for aarch64
>> Multi-arch related tests under gdb.multi are to compile programs with
>> the same compiler but different compiler options (-m64 vs -m32). However,
>> different compilers are needed to compile both aarch64 program and
>> arm (aarch32) program. This patch is to adjust these test cases to
>> compile programs in different modes with different compiler.
>> When we use gcc for arm-linux target, its file name can be different,
>> arm-linux-gnueabihf-gcc, arm-linux-gnueabi-gcc, or arm-none-linux-gnueabi-gcc,
>> so I add a variable ARM_CC_FOR_TARGET, so that user can set the name
>> of gcc for arm-linux target on aarch64, like:
>> $ make check RUNTESTFLAGS='ARM_CC_FOR_TARGET=arm-linux-gnueabihf-gcc multi-arch.exp'
>> gdb/testsuite:
>> 2015-07-07 Yao Qi <yao.qi@linaro.org>
>> * gdb.multi/multi-arch-exec.exp: Set march1 and march2 to "" if target
>> is aarch64. If target is aarch64, set compiler=${ARM_CC_FOR_TARGET}
>> if it exists.
>> * gdb.multi/multi-arch.exp: Likewise.
>>
>> ~~~~~
>>
>> I guess the issue is that nobody ever remembers to set ARM_CC_FOR_TARGET, or even
>> knows about it.
>
> Yeah. As a general comment, I always have to stop and think about the list of things that need
> to be installed in order for GDB's testsuite to run all/most of the tests.
Yes. I think a nice solution for that would be to have a script under gdb/contrib/ that installs
all the build & test dependencies on per distro basis. We have some of that in the old buildbot
wiki:
https://sourceware.org/gdb/wiki/BuildBot#Buildslave_configuration
and also mjw's new buildbot infrastructure also is gaining some docker scripts that know the same.
But I think putting it in gdb/contrib/ would be better so that everyone has easy access to it.
>
> If you're missing something, most of the time things show up as UNTESTED/UNSUPPORTED. It
> would be nice to have a stable list of things we need to have complete (as much as possible)
> testsuite coverage.
>
> Having to set these options by hand is quite obscure as well.
Yes, hence my proposed patch in the follow up email. I think that we should strive to make
just "make check" (with no options) Just Work.
>
>>
>> IWBN if the aarch64 bots people have access to tested with ARM_CC_FOR_TARGET, if they
>> aren't already.
>
> I think it is a less common scenario. Yes, this is supported, but my feeling is that people
> seldom use this. Which explains why nobody complained, and some are surprised this even works.
>
A 64-bit program can always exec a 32-bit program. Likewise the other way around. That should be
debuggable with a single gdb.
As you say, it's supported. So, better test it routinely. Not testing it doesn't gain us anything,
other than leading to bitrot, as has happened.
>>
>> Maybe it would be possible to come up with a way to default ARM_CC_FOR_TARGET to
>> something that works for most people when testing aarch64, somehow.
> The problem is that a compiler is not enough to make things run fine. If you have an aarch64
> Ubuntu, for example, you'd need to add armhf as an architecture option and install both the
> compiler and the libraries (libc6:armhf mostly).
That is not an issue specific to aarch64. On x86-64, you need to install extra runtime
packages to test -m32 too, just the compiler isn't enough, and those packages aren't installed
by default.
>
> Another problem is that not every processor/kernel supports running a 32-bit process in a
> 64-bit environment. This makes things more complicated.
>
Why "more complicated"? If you're worried about FAILs in the testsuite, then we can e.g. make it run
the 32-bit program once outside gdb to check that running 32-bits works. If that fails, then
we don't run the test. Seems simple, not complicated.
next prev parent reply other threads:[~2022-06-08 10:12 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 14:30 [PATCH 0/5] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-05-31 14:30 ` [PATCH 1/5] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-01 7:58 ` Luis Machado
2022-05-31 14:30 ` [PATCH 2/5] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-05-31 14:30 ` [PATCH 3/5] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-01 8:01 ` Luis Machado
2022-05-31 14:30 ` [PATCH 4/5] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-05-31 16:04 ` John Baldwin
2022-05-31 17:22 ` Andrew Burgess
2022-05-31 14:30 ` [PATCH 5/5] gdb: native target invalid architecture detection Andrew Burgess
2022-05-31 16:08 ` John Baldwin
2022-05-31 16:51 ` Andrew Burgess
2022-06-01 8:25 ` Luis Machado
2022-06-01 21:06 ` John Baldwin
2022-06-01 21:21 ` Christophe Lyon
2022-06-02 14:56 ` John Baldwin
2022-06-06 14:38 ` Andrew Burgess
2022-06-06 17:48 ` Andrew Burgess
2022-06-07 11:03 ` Luis Machado
2022-06-07 18:42 ` Pedro Alves
2022-06-07 20:15 ` Pedro Alves
2022-06-08 8:18 ` Luis Machado
2022-06-08 10:17 ` Pedro Alves
2022-06-08 7:54 ` Luis Machado
2022-06-08 10:12 ` Pedro Alves [this message]
2022-06-08 11:20 ` [PATCH v2] aarch64: Add fallback if ARM_CC_FOR_TARGET not set (was: Re: [PATCH 5/5] gdb: native target invalid architecture detection) Pedro Alves
2022-06-08 12:50 ` Luis Machado
2022-06-08 13:23 ` Pedro Alves
2022-06-08 13:38 ` Andrew Burgess
2022-06-08 19:01 ` John Baldwin
2022-06-08 21:48 ` Pedro Alves
2022-06-09 16:31 ` John Baldwin
2022-06-10 13:08 ` [PATCHv2 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 3/6] gdb/arm: avoid undefined behaviour in arm_frame_is_thumb Andrew Burgess
2022-06-10 15:21 ` Luis Machado
2022-06-10 15:49 ` Andrew Burgess
2022-06-10 16:29 ` Luis Machado
2022-06-10 13:08 ` [PATCHv2 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-10 16:35 ` Luis Machado
2022-06-10 13:08 ` [PATCHv2 5/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-06-10 13:08 ` [PATCHv2 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-10 16:20 ` John Baldwin
2022-06-10 16:31 ` Luis Machado
2022-06-13 16:15 ` [PATCHv3 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 3/6] gdb: select suitable thread for gdbarch_adjust_breakpoint_address Andrew Burgess
2022-06-14 9:45 ` Luis Machado
2022-06-14 14:05 ` Andrew Burgess
2022-06-24 16:58 ` Pedro Alves
2022-06-13 16:15 ` [PATCHv3 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-13 16:15 ` [PATCHv3 5/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-06-24 18:15 ` Pedro Alves
2022-06-13 16:15 ` [PATCHv3 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-24 19:23 ` Pedro Alves
2022-06-27 16:27 ` Andrew Burgess
2022-06-27 21:38 ` Pedro Alves
2022-06-28 10:37 ` Andrew Burgess
2022-06-28 12:42 ` [PATCH v2] gdb+gdbserver/Linux: avoid reading registers while going through shell (was: Re: [PATCHv3 6/6] gdb: native target invalid architecture detection) Pedro Alves
2022-06-28 14:21 ` Andrew Burgess
2022-06-29 15:17 ` Simon Marchi
2022-06-29 16:22 ` [PATCH] Fix GDBserver regression due to change to avoid reading shell registers Pedro Alves
2022-06-29 16:38 ` Simon Marchi
2022-06-30 9:33 ` [PATCHv3 6/6] gdb: native target invalid architecture detection Andrew Burgess
2022-06-30 11:44 ` Pedro Alves
2022-07-11 10:47 ` Andrew Burgess
2022-06-24 10:15 ` [PATCHv3 0/6] Handle trying to use a native target with the wrong binary Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 0/6] Detect invalid casts of gdbarch_tdep structures Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 1/6] gdb/arm: move fetch of arm_gdbarch_tdep to a more inner scope Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 2/6] gdb/mips: rewrite show_mask_address Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 3/6] gdb: select suitable thread for gdbarch_adjust_breakpoint_address Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 4/6] gdb: move the type cast into gdbarch_tdep Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 5/6] gdbsupport: add checked_static_cast Andrew Burgess
2022-06-28 14:28 ` [PATCHv4 6/6] gdb: ensure the cast in gdbarch_tdep is valid Andrew Burgess
2022-07-11 10:46 ` [PATCHv4 0/6] Detect invalid casts of gdbarch_tdep structures Andrew Burgess
2022-07-21 18:21 ` Andrew Burgess
2022-07-22 0:50 ` Luis Machado
2022-07-23 0:02 ` [PATCH] Rename gdbarch_tdep template function to gdbarch_tdep_cast for g++ 4.8 Mark Wielaard
2022-07-25 11:19 ` Andrew Burgess
2022-07-25 11:27 ` Mark Wielaard
2022-07-26 11:05 ` Andrew Burgess
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=22be6164-79d7-c0f7-1b1b-c633be452e81@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--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).