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/29694] New: [gdb, gdb-index] FAIL: gdb.cp/stub-array-size.exp: print sizeof(a)/sizeof(a[0])
Date: Sun, 16 Oct 2022 07:41:21 +0000 [thread overview]
Message-ID: <bug-29694-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29694
Bug ID: 29694
Summary: [gdb, gdb-index] FAIL: gdb.cp/stub-array-size.exp:
print sizeof(a)/sizeof(a[0])
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: ---
On openSUSE Tumbleweed with test-case gdb.cp/stub-array-size.exp and target
board cc-with-gdb-index, I run into:
...
(gdb) print sizeof(a)/sizeof(a[0])^M
Division by zero^M
(gdb) FAIL: gdb.cp/stub-array-size.exp: print sizeof(a)/sizeof(a[0])
...
This is a regression since gdb 12 branch point.
Bisects to:
...
6acc36f71dfc60e357496174672103f133f85e97 is the first bad commit
commit 6acc36f71dfc60e357496174672103f133f85e97
Author: Tom Tromey <tromey@adacore.com>
Date: Thu Apr 21 09:37:24 2022 -0600
Fix method naming bug in new DWARF indexer
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-16 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 7:41 vries at gcc dot gnu.org [this message]
2022-10-16 7:41 ` [Bug symtab/29694] " vries at gcc dot gnu.org
2022-10-16 7:43 ` vries at gcc dot gnu.org
2022-10-16 15:39 ` vries at gcc dot gnu.org
2022-10-16 16:10 ` tromey at sourceware dot org
2022-10-17 3:59 ` vries at gcc dot gnu.org
2022-10-17 15:48 ` tromey at sourceware dot org
2022-10-17 15:56 ` tromey at sourceware dot org
2022-10-17 16:04 ` tromey at sourceware dot org
2022-10-17 19:41 ` tromey at sourceware dot org
2022-10-21 16:13 ` cvs-commit at gcc dot gnu.org
2022-10-21 16:14 ` tromey at sourceware dot 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-29694-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).