From: Joel Brobecker <brobecker@adacore.com>
To: John Baldwin <jhb@freebsd.org>
Cc: gdb-patches@sourceware.org, 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: Wed, 20 Apr 2016 18:50:00 -0000 [thread overview]
Message-ID: <20160420185022.GA4078@adacore.com> (raw)
In-Reply-To: <1637407.eeDNHfBBCL@ralph.baldwin.cx>
> 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.)
Thanks for the info! Given what you said, I also think it is fair to
drop a.out. Should have done that a while ago, actually! :-)
--
Joel
next prev parent reply other threads:[~2016-04-20 18:50 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
2016-04-20 18:50 ` Joel Brobecker [this message]
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=20160420185022.GA4078@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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