public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Tom Tromey via Gdb-patches <>
Cc: Tom Tromey <>
Subject: Re: [PATCH] Do not record a rejected target description
Date: Tue, 14 Feb 2023 08:16:06 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Tom Tromey via Gdb-patches's message of "Thu, 12 Jan 2023 12:33:56 -0700")

>>>>> "Tom" == Tom Tromey via Gdb-patches <> writes:

Tom> When connecting to a certain target, gdb issues a warning about the
Tom> target description:

Tom>     (gdb) target remote localhost:7947
Tom>     Remote debugging using localhost:7947
Tom>     warning: Architecture rejected target-supplied description

Tom> If you then kill the inferior and change the exec-file, this will
Tom> happen:

Tom>     (gdb) file bar
Tom>     Architecture of file not recognized.

Tom> After this, debugging doesn't work very well.

Tom> What happens here is that, despite the warning,
Tom> target_find_description records the downloaded description in the
Tom> target_desc_info.  Then the "file" command ends up calling
Tom> set_gdbarch_from_file, which uses that description.

Tom> It seems to me that, because the architecture rejected the
Tom> description, it should not be used.  That is what this patch
Tom> implements.

We've been using this internally with our misbehaving target and it is
fine, but I'd appreciate someone else's review.


  reply	other threads:[~2023-02-14 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:33 Tom Tromey
2023-02-14 15:16 ` Tom Tromey [this message]
2023-02-14 15:48 ` Andrew Burgess
2023-02-14 17:27   ` Tom Tromey
2023-02-15 12:56     ` Andrew Burgess
2023-02-15 15:59       ` Tom Tromey
2023-02-15 21:19         ` Simon Marchi
2023-02-15 21:38           ` Tom Tromey
2023-02-16 19:20           ` Tom Tromey
2023-02-16 19:33             ` Simon Marchi
2023-02-17 10:19             ` Andrew Burgess
2023-02-17 14:09               ` Tom Tromey
2023-02-17 22:29                 ` 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:

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