From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: gdb-patches@sourceware.org
Cc: luca.pizzamiglio@gmail.com
Subject: [RFC] Removing old core file sniffer support (affects FreeBSD/alpha)
Date: Fri, 28 Nov 2014 16:26:00 -0000 [thread overview]
Message-ID: <201411281626.sASGQcCB026552@d03av02.boulder.ibm.com> (raw)
Hello,
after a transition period of more than a decade, we are really close to
actually moving all targets to the new tdep core file support (enabling
cross-debugging of core files and core file generation), and removing
the old-style long-deprecated native core file sniffer support.
I've posted (untested) patches moving four of the remaining targets
Linux/CRIS:
https://sourceware.org/ml/gdb-patches/2014-11/msg00707.html
GNU Hurd:
https://sourceware.org/ml/gdb-patches/2014-11/msg00708.html
Sparc Solaris:
https://sourceware.org/ml/gdb-patches/2014-11/msg00709.html
NetBSD/arm:
https://sourceware.org/ml/gdb-patches/2014-11/msg00714.html
Once those are in, there is just one more target remaining: FreeBSD/alpha.
I have an untested patch for this as well, but I'm wondering
whether this is worth it, as FreeBSD apparently has long stopped
supporting the Alpha platform (last available in FreeBSD 6.4,
which has been unsupported since end of 2010, if I'm reading
the web site correctly).
Given that, should we just remove FreeBSD/alpha support from
mainline GDB sources?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next reply other threads:[~2014-11-28 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 16:26 Ulrich Weigand [this message]
2014-11-28 16:33 ` Luca Pizzamiglio
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=201411281626.sASGQcCB026552@d03av02.boulder.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luca.pizzamiglio@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).