public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26243] Handle line number 0 in line table produced by clang
Date: Fri, 17 Jul 2020 15:00:24 +0000 [thread overview]
Message-ID: <bug-26243-4717-aoiGK42Noc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26243-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26243
--- Comment #13 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Pedro Alves from comment #12)
> > I.e., seems like either there's a bug elsewhere, where bar2's length is
> > determined, or the testcase has a bug. The other two calls to foo should be
> > part of the function too.
>
> It's the latter - a simple typo:
>
> diff --git c/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
> w/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
> index e322f777082..acf16848e82 100644
> --- c/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
> +++ w/gdb/testsuite/gdb.dwarf2/dw2-line-number-zero.exp
> @@ -74,7 +74,7 @@ Dwarf::assemble $asm_file {
> {external 1 flag}
> {name bar2}
> {low_pc $bar2_start addr}
> - {high_pc "$bar2_start + $main_length" addr}
> + {high_pc "$bar2_start + $bar2_length" addr}
> }
> }
> }
>
Sorry about that. I've now found out that I could have used this instead:
...
{external 1 flag}
{MACRO_AT_func {bar2}}
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-17 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 13:11 [Bug symtab/26243] New: " vries at gcc dot gnu.org
2020-07-15 14:31 ` [Bug symtab/26243] " vries at gcc dot gnu.org
2020-07-15 14:36 ` vries at gcc dot gnu.org
2020-07-15 15:09 ` vries at gcc dot gnu.org
2020-07-15 15:20 ` andrew.burgess at embecosm dot com
2020-07-15 15:47 ` vries at gcc dot gnu.org
2020-07-15 22:05 ` vries at gcc dot gnu.org
2020-07-16 17:59 ` vries at gcc dot gnu.org
2020-07-16 19:18 ` simark at simark dot ca
2020-07-16 20:46 ` palves at redhat dot com
2020-07-16 20:51 ` palves at redhat dot com
2020-07-16 21:18 ` palves at redhat dot com
2020-07-16 22:22 ` palves at redhat dot com
2020-07-17 15:00 ` vries at gcc dot gnu.org [this message]
2020-07-20 13:00 ` andrew.burgess at embecosm dot com
2020-07-20 13:15 ` palves at redhat dot com
2020-07-24 22:23 ` cvs-commit at gcc dot gnu.org
2020-07-24 22:33 ` vries at gcc dot gnu.org
2020-09-03 5:19 ` jaydeepchauhan1494 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-26243-4717-aoiGK42Noc@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).