public inbox for
 help / color / mirror / Atom feed
From: Luis Machado <>
To: Fabian Cenedese <>,
Subject: Re: Internal error with gcc 4.7 elffile
Date: Tue, 8 Mar 2022 08:58:09 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20220308075403.BD4194ACEF70@macserver.private>


On 3/8/22 07:54, Fabian Cenedese wrote:
> Hello
> I'm currently working with a gdb, used for cross-compiled
> .elf files for PowerPC and ARM. There are no problems with elf files from
> gcc 7 or 10 or clang 12. However an elf file from a gcc 4.7 leads to an
> internal error in gdb. Somehow it can't detect the architecture. It should
> be PowerPC as readelf is able to confirm.
> ----------------------------
> Reading symbols from inos_testing.elf...
> ../../gdb/gdbarch.c:3576: internal-error: bool gdbarch_elf_make_msymbol_special_p(gdbarch*): Assertion `gdbarch != NULL' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session?
> ----------------------------
> First I wanted to know if this should work at all or is gcc 4.7 too old to
> be supported by gdb 11? If it should still work, is this a known problem?
> I couldn't find bugs mentioning gdbarch.c
> The same elffile works perfectly fine with a gdb 7.6. A workaround seems
> to be to first start gdb, then set architecture before loading elffile.

Although gcc 4.7 is fairly old, it could be a bug or deficiency in GDB.
It might be the case that GDB is not finding what it is looking for,
thus ending up in an inconsistent state.

If you have a reproducer, it might be worth opening a bug ticket against
GDB so developers can take a look:
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

      reply	other threads:[~2022-03-08  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  7:54 Fabian Cenedese
2022-03-08  8:58 ` Luis Machado [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).