From: Tom Tromey <tromey@redhat.com>
To: GDB Development <gdb@sourceware.org>
Subject: proposed symbol format deprecations
Date: Thu, 13 Dec 2012 16:04:00 -0000 [thread overview]
Message-ID: <87zk1i3psj.fsf@fleche.redhat.com> (raw)
I've been working on some changes that touch most of the symbol readers,
and I notice that a couple of them are barely active -- somread.c and
mdebugread.c.
somread.c is used to read the HP-UX SOM format:
http://en.wikipedia.org/wiki/System_Object_Model_%28file_format%29
It is only used on 32-bit PA-RISC systems. somread.c can't even be
built on other machines as it requires the HP-UX <syms.h>.
mdebugread.c is used to read the ECOFF format:
http://en.wikipedia.org/wiki/ECOFF
It is most recently used, I think, by Tru64.
I would like to propose deprecating both of these readers.
I think somread.c hasn't been actively developed in some time. 32-bit
PA-RISC machines seem hard to come by nowadays.
mdebugread.c also seems unused. I recently discovered that it doesn't
use buildsym to make blocks, so with the "global_block" changes it will
probably cause gdb crashes if it is actually used. (It also leaks all
the blocks it creates ... quite bad.)
Specifically I propose that we announce the deprecations in NEWS and
remove the files from the build (but leave them in the source tree) for
gdb 7.6. Then, after 7.6 is out, we remove the files from trunk.
If someone steps forward to maintain the code, we can easily resurrect
it.
Tom
next reply other threads:[~2012-12-13 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 16:04 Tom Tromey [this message]
2012-12-14 8:37 ` Tristan Gingold
2012-12-14 15:56 ` Tom Tromey
2012-12-14 18:07 ` Tom Tromey
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=87zk1i3psj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@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).