Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: proposed symbol format deprecations
Date: Fri, 14 Dec 2012 18:07:00 -0000	[thread overview]
Message-ID: <87txrozew9.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")

Tristan> [ bfd for HP/PA is able to be cross-built ]

Thanks for the hint.

Tristan> You should talk with the HP/PA GCC maintainer, as AFAIK only
Tristan> gdb is able to debug gcc-generated binaries.

He replied off-list to say that this is what he uses for all his GCC
hacking.

He's going to test some patches for me.
I have a patch to make it possible to build somread.c anywhere the BFD
target is enabled, so that's a start.

So, consider this one dropped from the deprecation list.
I'd still like to deprecate mdebugread.c though.

Tom


      parent reply	other threads:[~2012-12-14 18:07 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
2012-12-14 18:07   ` Tom Tromey [this message]

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=87txrozew9.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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