public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17276] gdb needs to coalesce multiple line number entries for the same (non-prologue) line
Date: Sat, 23 Aug 2014 00:29:00 -0000	[thread overview]
Message-ID: <bug-17276-4717-hJyv5HDalV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17276-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17276

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  a05a36a5fc98c816381b25c37e8aa971cc86c28d (commit)
      from  9bda4a968f56cb61b832cdbdabf09a84eab140ab (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a05a36a5fc98c816381b25c37e8aa971cc86c28d

commit a05a36a5fc98c816381b25c37e8aa971cc86c28d
Author: Doug Evans <dje@google.com>
Date:   Fri Aug 22 17:25:59 2014 -0700

    Fix pr 17276.

    See the description here:
    https://sourceware.org/ml/gdb-patches/2014-08/msg00283.html

    This patch keeps track of whether the current line has seen a
    non-zero discriminator, and if so coalesces consecutive entries
    for the same line (by ignoring all entries after the first).

    gdb/ChangeLog:

        PR 17276
        * dwarf2read.c (dwarf_record_line_p): New function.
        (dwarf_decode_lines_1): Ignore subsequent line number entries
        for the same line if any entry had a non-zero discriminator.

    gdb/testsuite/ChangeLog:

        * gdb.dwarf2/dw2-single-line-discriminators.S: New file.
        * gdb.dwarf2/dw2-single-line-discriminators.c: New file.
        * gdb.dwarf2/dw2-single-line-discriminators.exp: New file.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog                                      |    7 +
 gdb/dwarf2read.c                                   |  108 +++++++-
 gdb/testsuite/ChangeLog                            |    7 +
 .../gdb.dwarf2/dw2-single-line-discriminators.S    |  281 ++++++++++++++++++++
 .../gdb.dwarf2/dw2-single-line-discriminators.c    |   31 +++
 .../gdb.dwarf2/dw2-single-line-discriminators.exp  |   49 ++++
 6 files changed, 471 insertions(+), 12 deletions(-)
 create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-single-line-discriminators.S
 create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-single-line-discriminators.c
 create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-single-line-discriminators.exp

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2014-08-23  0:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 18:35 [Bug symtab/17276] New: " dje at google dot com
2014-08-23  0:29 ` cvs-commit at gcc dot gnu.org [this message]
2014-08-23 22:08 ` [Bug symtab/17276] " xdje42 at gmail dot com

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=bug-17276-4717-hJyv5HDalV@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).