From: Randolph Chung <randolph@tausq.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [hppa-hpux] Core file support for hppa64-hp-hpux11.11
Date: Thu, 17 Nov 2005 15:52:00 -0000 [thread overview]
Message-ID: <437C7E07.5050804@tausq.org> (raw)
In-Reply-To: <200511171244.jAHCi9RY004505@elgar.sibelius.xs4all.nl>
> Don't think this is right. Is it needed at all? If it is, then we
> should try to do this differently. The mere fact that the BFD target
> is elf64-hppa doesn't imply that this is a HP-UX ELF core file does it?
Well, the osabi sniffer doesn't say that it's a corefile, it just says
it's a HPUX ELF file. As for whether "elf64-hppa" means hpux, currently
bfd/elf64-hppa.c only supports two targets, hpux and linux, and linux is
"elf64-hppa-linux". I know this is not very nice. Do you have any other
suggestions?
randolph
next prev parent reply other threads:[~2005-11-17 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 12:56 Randolph Chung
2005-11-17 14:46 ` Mark Kettenis
2005-11-17 15:52 ` Randolph Chung [this message]
2005-11-17 16:02 ` Mark Kettenis
2005-11-18 3:37 ` Randolph Chung
2005-11-18 4:44 ` Mark Kettenis
2005-11-18 13:49 ` Randolph Chung
2005-11-18 15:30 ` Mark Kettenis
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=437C7E07.5050804@tausq.org \
--to=randolph@tausq.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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