From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
Simon Marchi <simon.marchi@ericsson.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [RFC] Remove all a.out support and gc no-longer-supported OS ABIs? (Re: [PATCH] Avoid spaces in osabi names)
Date: Tue, 19 Apr 2016 19:26:00 -0000 [thread overview]
Message-ID: <1637407.eeDNHfBBCL@ralph.baldwin.cx> (raw)
In-Reply-To: <56DF7DA6.4080704@redhat.com>
On Wednesday, March 09, 2016 01:34:30 AM Pedro Alves wrote:
> Yeah. We have some left over bits that reference it, but I think
> we can get rid of them.
>
> I think we can get rid of everything a.out too. We removed most
> support for a.out BSD targets a while ago, but AFAICS, some of the
> a.out support is still in place for debugging BSD core dumps in
> a.out format. I found some left over SunOS a.out support too, which
> we no longer support either.
>
> It is my understanding that OpenBSD switched to ELF core dumps
> several years ago. NetBSD's core man page talks about ELF-format
> core dumps too.
>
> Mark, do you know whether there's any reason we should keep a.out
> support longer?
With my FreeBSD hat on, I think it would be fine to drop a.out support.
FreeBSD still permits running a.out binaries, but if someone really wants
to debug that they can probably grab an older snapshot of gdb if they
really care. (FreeBSD has used ELF for binaries and cores since 3.0
which was released in October 1998. The last release to ship a.out
binaries was 2.2.8 released in November of 1998.)
--
John Baldwin
next prev parent reply other threads:[~2016-04-19 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 19:02 [PATCH] Avoid spaces in osabi names Pedro Alves
2016-03-07 19:12 ` Simon Marchi
2016-03-09 1:34 ` [RFC] Remove all a.out support and gc no-longer-supported OS ABIs? (Re: [PATCH] Avoid spaces in osabi names) Pedro Alves
2016-04-19 19:26 ` John Baldwin [this message]
2016-04-20 18:50 ` Joel Brobecker
2016-04-22 13:14 ` Pedro Alves
2016-12-09 16:25 ` [pushed] " Pedro Alves
2016-03-08 20:59 ` [PATCH] Avoid spaces in osabi names Joel Brobecker
2016-03-09 15:58 ` Pedro Alves
2016-12-09 16:57 ` [PATCH] Don't allow whitespace in enum values of enum commands (Re: [PATCH] Avoid spaces in osabi names) Pedro Alves
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=1637407.eeDNHfBBCL@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
/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