From: Luis Machado <luis.machado@arm.com>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix crash with "maintenance print arc"
Date: Wed, 27 Apr 2022 12:00:27 +0100 [thread overview]
Message-ID: <85bb4b17-fa07-f8c9-8d46-3a8094a107cf@arm.com> (raw)
In-Reply-To: <871qxiq00y.fsf@redhat.com>
On 4/27/22 11:43, Andrew Burgess wrote:
> Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>
>> While doing something else, I noticed GDB crashed with
>> "maintenance print arc".
>
> I tried building current master, and "maintenance print arc" completes
> just fine (for me). Can you give more details on how to reproduce the
> crash?
There is not much more to it other than building a 64-bit aarch64 Linux
Ubuntu 20.04 master with --enable-targets=all. I can reproduce it quite
reliably.
--
(gdb) maint print arc
Fatal signal: Segmentation fault
----- Backtrace -----
0xad07a3 gdb_internal_backtrace_1
../../../repos/binutils-gdb/gdb/bt-utils.c:122
0xad07a3 _Z22gdb_internal_backtracev
../../../repos/binutils-gdb/gdb/bt-utils.c:168
0xb8d6cd handle_fatal_signal
../../../repos/binutils-gdb/gdb/event-top.c:946
0xb8d761 handle_sigsegv
../../../repos/binutils-gdb/gdb/event-top.c:1019
0xf72f47bf ???
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
Segmentation fault (core dumped)
--
next prev parent reply other threads:[~2022-04-27 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:07 Luis Machado
2022-04-27 10:43 ` Andrew Burgess
2022-04-27 11:00 ` Luis Machado [this message]
2022-04-28 15:27 ` Tom Tromey
2022-04-29 10:20 ` Andrew Burgess
2022-04-28 15:26 ` Tom Tromey
2022-04-29 8:58 ` Luis Machado
2022-04-29 10:18 ` Andrew Burgess
2022-04-29 10:39 ` Luis Machado
2022-04-29 11:25 ` Pedro Alves
2022-05-05 9:31 ` Luis Machado
2022-05-27 13:34 ` Tom Tromey
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=85bb4b17-fa07-f8c9-8d46-3a8094a107cf@arm.com \
--to=luis.machado@arm.com \
--cc=aburgess@redhat.com \
--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).