From: Tom Tromey <tromey@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: GDB Development <gdb@sourceware.org>,
John David Anglin <dave.anglin@bell.net>
Subject: Re: proposed symbol format deprecations
Date: Fri, 14 Dec 2012 15:56:00 -0000 [thread overview]
Message-ID: <87pq2c1vd2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C5C1CE6-64E0-4864-AB22-F5AF52E9E707@adacore.com> (Tristan Gingold's message of "Fri, 14 Dec 2012 09:37:33 +0100")
CCing John.
John, the context here is this:
Tom> I've been working on some changes that touch most of the symbol readers,
Tom> and I notice that a couple of them are barely active -- somread.c and
Tom> mdebugread.c.
Tom>
Tom> somread.c is used to read the HP-UX SOM format:
Tom>
Tom> http://en.wikipedia.org/wiki/System_Object_Model_%28file_format%29
Tom>
Tom> It is only used on 32-bit PA-RISC systems. somread.c can't even be
Tom> built on other machines as it requires the HP-UX <syms.h>.
Tristan> You should talk with the HP/PA GCC maintainer, as AFAIK only
Tristan> gdb is able to debug gcc-generated binaries.
John, is 32-bit HP/PA using SOM objects a live target?
Tom
next prev parent reply other threads:[~2012-12-14 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 16:04 Tom Tromey
2012-12-14 8:37 ` Tristan Gingold
2012-12-14 15:56 ` Tom Tromey [this message]
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=87pq2c1vd2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dave.anglin@bell.net \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.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