public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18404] [8 Regression] gdb fails to handle EM_486/EM_IAMCU binary
Date: Thu, 16 Feb 2023 16:34:52 +0000	[thread overview]
Message-ID: <bug-18404-4717-J5mbYp7ucg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18404-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18404

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Tom Tromey from comment #2)
> Is this still relevant / necessary?

Yes.

> I see bfd_arch_iamcu in BFD still, and nothing in gdb.
> I don't know how to test this but the patch looks essentially
> fine to me.  It would just need an update for some renamings in gdb.

$ cat x.c
#include <stdio.h>

int
main ()
{
  printf ("hello\n");
  return 0;
}
$ gcc -m32 -g -static x.c
$ elfedit --output-mach=iamcu a.out
$ gdb a.out

will reproduce it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-02-16 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 19:56 [Bug gdb/18404] New: " hjl.tools at gmail dot com
2015-05-12 19:57 ` [Bug gdb/18404] " hjl.tools at gmail dot com
2023-02-15 17:09 ` tromey at sourceware dot org
2023-02-16 16:34 ` hjl.tools at gmail dot com [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:
  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=bug-18404-4717-J5mbYp7ucg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).