From: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "brobecker@adacore.com" <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFA bug fix -- x86-64 stabs and deprecated fp register
Date: Mon, 01 Dec 2014 16:42:00 -0000 [thread overview]
Message-ID: <16828.1417452115@usendtaylorx2l> (raw)
In-Reply-To: <201411301859.sAUIxFTU016422@glazunov.sibelius.xs4all.nl>
Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> But any effort is much better spent on switching to DWARF2. STABS
> support ws already considered obsolete when AMD64 support was added to
> GDB more than a decade ago.
For current systems we have earlier this year switched to DWARF, but we
will need to support STABS for legacy systems for a few years.
As far as it being obsolete, I asked about its status in January 2013 on
the gdb list. My take away from that discussion was that it was not
deprecated nor obsolete and that it was being maintained; but, that new
development was focused on DWARF.
[As far as DWARF goes, we use DWARF 3+/4 and GCC 4.7+ as we use -g3 to
get macro debug information and want the strings to be consolidated.]
next prev parent reply other threads:[~2014-12-01 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 20:58 David Taylor
2014-11-30 15:20 ` Joel Brobecker
2014-11-30 18:59 ` Mark Kettenis
2014-12-01 16:42 ` David Taylor [this message]
2014-12-03 3:19 ` Joel Brobecker
2014-12-01 16:30 ` David Taylor
2014-12-03 3:50 ` Joel Brobecker
2014-12-03 17:31 ` Doug Evans
2014-12-04 3:20 ` Joel Brobecker
2014-12-05 13:38 ` Mark Kettenis
2014-12-03 3:43 ` Doug Evans
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=16828.1417452115@usendtaylorx2l \
--to=dtaylor@usendtaylorx2l.lss.emc.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).