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/30797] [gdb/symtab, cc-with-dwz] FAIL: gdb.base/setshow.exp: test_setshow_annotate: annotation_level 1
Date: Tue, 29 Aug 2023 09:27:38 +0000 [thread overview]
Message-ID: <bug-30797-4717-oZY34iE07i@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30797-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30797
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
So there's the problem of repetition. In info_line_command, we have the
following sals:
...
(gdb) p sals
$1 = {m_array = 0x2d6b420, m_size = 2}
(gdb) p sals[0]
$2 = (symtab_and_line &) @0x2d6b420: {pspace = 0x29eb280, symtab = 0x2d4c960,
symbol = 0x0, section = 0x0,
msymbol = 0x0, line = 1, pc = 0, end = 0, explicit_pc = false, explicit_line
= true, is_stmt = false, prob = 0x0,
objfile = 0x0}
(gdb) p sals[1]
$3 = (symtab_and_line &) @0x2d6b478: {pspace = 0x29eb280, symtab = 0x2d4c960,
symbol = 0x0, section = 0x0,
msymbol = 0x0, line = 1, pc = 0, end = 0, explicit_pc = false, explicit_line
= true, is_stmt = false, prob = 0x0,
objfile = 0x0}
...
The two items are identical.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-29 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 13:46 [Bug symtab/30797] New: " vries at gcc dot gnu.org
2023-08-29 9:27 ` vries at gcc dot gnu.org [this message]
2023-08-29 9:30 ` [Bug symtab/30797] " vries at gcc dot gnu.org
2023-08-29 10:10 ` vries at gcc dot gnu.org
2023-08-29 11:02 ` vries at gcc dot gnu.org
2023-08-29 11:50 ` vries at gcc dot gnu.org
2023-08-31 10:38 ` vries at gcc dot gnu.org
2023-09-06 8:15 ` cvs-commit at gcc dot gnu.org
2023-09-07 21:27 ` vries at gcc dot gnu.org
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-30797-4717-oZY34iE07i@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).