public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/6] DWARF Two Level Line Tables
Date: Thu, 28 May 2015 17:12:00 -0000	[thread overview]
Message-ID: <CADPb22R5iaFgYYWiQnSs3g5yE0iJZFC2dR1YSWMYwe=j4Ka85Q@mail.gmail.com> (raw)
In-Reply-To: <yjt2egou7zsx.fsf@ruffy.mtv.corp.google.com>

On Thu, Mar 12, 2015 at 12:58 PM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> This patch set adds Two Level Line Tables support to gdb,
> as well as support for the DWARF 5 line table extensions.
>
> http://wiki.dwarfstd.org/index.php?title=TwoLevelLineTables
> http://www.dwarfstd.org/ShowIssue.php?issue=140906.1
> http://www.dwarfstd.org/ShowIssue.php?issue=140724.1
>
> The current version of the patch uses a gross hack because
> consumers of debug info, including gdb, are not aggressive
> enough in rejecting versions they don't understand.
> So that existing gdbs won't crash when given the new line table
> we create a DWARF 4 line header, and tuck the guts of the
> two line tables (logicals + actuals) in something that looks
> like a single entry.
> Fortunately 7.9 won't crash, so the plan is to hopefully do
> something more sensible.
>
> The patch has been regression tested with existing debug info,
> as well as the new two-level-line-table support on the google-4.9.x
> gcc branch, and the binutils users/ccoutant/two-level-line-tables branch.

I've committed the first four patches in this series,
which were just cleanups.

The remaining two patches add support for DWARF v5 line
tables as well as the proposed two level line tables.
Since stock gcc doesn't generate these yet my plan
is to hold off committing them for now.
I'm happy to commit them early if someone needs/wants me too.

      parent reply	other threads:[~2015-05-28 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 19:59 Doug Evans
2015-03-13 17:32 ` Yao Qi
2015-03-13 17:44   ` Doug Evans
2015-05-28 17:12 ` Doug Evans [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='CADPb22R5iaFgYYWiQnSs3g5yE0iJZFC2dR1YSWMYwe=j4Ka85Q@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@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).