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] New: [gdb/symtab, cc-with-dwz] FAIL: gdb.base/setshow.exp: test_setshow_annotate: annotation_level 1
Date: Fri, 25 Aug 2023 13:46:31 +0000	[thread overview]
Message-ID: <bug-30797-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30797
           Summary: [gdb/symtab, cc-with-dwz] FAIL: gdb.base/setshow.exp:
                    test_setshow_annotate: annotation_level 1
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With target board cc-with-dwz I run into:
...
FAIL: gdb.base/setshow.exp: test_setshow_annotate: annotation_level 2 (timeout)
FAIL: gdb.base/setshow.exp: test_setshow_annotate: annotation_level 1
...

The second one in more detail:
...
(gdb) PASS: gdb.base/setshow.exp: test_setshow_annotate: show annotate (1)
info line 1^M
Line 1 of "/data/vries/gdb/src/gdb/testsuite/gdb.base/setshow.c" is at address
0x400527 <main> but contains no code.^M
Line 1 of "/data/vries/gdb/src/gdb/testsuite/gdb.base/setshow.c" is at address
0x400527 <main> but contains no code.^M
(gdb) FAIL: gdb.base/setshow.exp: test_setshow_annotate: annotation_level 1
...

Let's try this with system gdb, based on 12.1:
...
$ gcc ./src/gdb/testsuite/gdb.base/setshow.c -g
$ gdb -q -batch a.out -ex "set annotate 1" -ex "info line 1"
Line 1 of "./src/gdb/testsuite/gdb.base/setshow.c" is at address 0x400517
<main> but contains no code.
��/data/vries/gdb/binutils-gdb.git/gdb/testsuite/gdb.base/setshow.c:1:0:beg:0x400517
$ dwz a.out
$ gdb -q -batch a.out -ex "set annotate 1" -ex "info line 1"
Line 1 of "./src/gdb/testsuite/gdb.base/setshow.c" is at address 0x400517
<main> but contains no code.
��/data/vries/gdb/binutils-gdb.git/gdb/testsuite/gdb.base/setshow.c:1:0:beg:0x400517
$
...

OK, so far so good, now with master:
...
$ gcc ./src/gdb/testsuite/gdb.base/setshow.c -g
$ gdb -q -batch a.out -ex "set annotate 1" -ex "info line 1"
Line 1 of "./src/gdb/testsuite/gdb.base/setshow.c" is at address 0x400517
<main> but contains no code.
��/data/vries/gdb/binutils-gdb.git/gdb/testsuite/gdb.base/setshow.c:1:0:beg:0x400517
$ dwz a.out
$ gdb -q -batch a.out -ex "set annotate 1" -ex "info line 1"
Line 1 of "./src/gdb/testsuite/gdb.base/setshow.c" is at address 0x400517
<main> but contains no code.
Line 1 of "./src/gdb/testsuite/gdb.base/setshow.c" is at address 0x400517
<main> but contains no code.
...

So this is a gdb 12 -> gdb 13 regression.

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

             reply	other threads:[~2023-08-25 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 13:46 vries at gcc dot gnu.org [this message]
2023-08-29  9:27 ` [Bug symtab/30797] " vries at gcc dot gnu.org
2023-08-29  9:30 ` 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@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).