public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29468] GDB test gdb.base/ctf-constvars.exp fails.
Date: Wed, 12 Oct 2022 16:06:11 +0000 [thread overview]
Message-ID: <bug-29468-4717-e8dlxDJlqe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29468-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29468
Carl E Love <cel at us dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #7 from Carl E Love <cel at us dot ibm.com> ---
OK, my bad. I did the testing in the wrong directory. Argh. So, when I build
and test using the correct build directory on PowerPC I get
(gdb) run
Starting program:
/home/carll/GDB/binutils-gdb-next-reverse-bkpt-over-sr/gdb/te\
stsuite/outputs/gdb.base/ctf-constvars/ctf-constvars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Breakpoint 1, 0x0000000010000698 in main ()
(gdb) print vox
$1 = 66 'B'
(gdb) PASS: gdb.base/ctf-constvars.exp: print vox
ptype vox
type = volatile char
(gdb) PASS: gdb.base/ctf-constvars.exp: ptype vox
print victuals
$2 = 67 'C'
(gdb) PASS: gdb.base/ctf-constvars.exp: print victuals
ptype victuals
type = volatile unsigned char
(gdb) PASS: gdb.base/ctf-constvars.exp: ptype victuals
print vixen
$3 = 200
(gdb) PASS: gdb.base/ctf-constvars.exp: print vixen
ptype vixen
type = volatile short
,,,
type = const volatile unsigned char [2]
(gdb) PASS: gdb.base/ctf-constvars.exp: ptype vegetation
testcase
/home/carll/GDB/binutils-gdb-next-reverse-bkpt-over-sr/gdb/testsuite/g\
db.base/ctf-constvars.exp completed in 0 seconds
=== gdb Summary ===
# of expected passes 56
Executing on host: /home/carll/bin/gdb -nw -nx -iex "set height 0" -iex "set
wi\
dth 0" --version (timeout = 300)
So, yes the patch does fix the error on PowerPC. Sorry for the confusion.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-12 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 20:30 [Bug gdb/29468] New: " cel at us dot ibm.com
2022-09-20 15:43 ` [Bug gdb/29468] " vries at gcc dot gnu.org
2022-09-27 15:34 ` vries at gcc dot gnu.org
2022-10-12 15:18 ` [Bug testsuite/29468] " vries at gcc dot gnu.org
2022-10-12 15:39 ` cel at us dot ibm.com
2022-10-12 15:55 ` vries at gcc dot gnu.org
2022-10-12 15:56 ` vries at gcc dot gnu.org
2022-10-12 16:06 ` cel at us dot ibm.com [this message]
2022-10-12 16:09 ` 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-29468-4717-e8dlxDJlqe@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).