From: Sachin Monga via Gdb <gdb@sourceware.org>
To: aburgess@redhat.com
Cc: carl Love <cel@linux.ibm.com>,
saurov.kanti.shyam@ibm.com, gdb@sourceware.org
Subject: Test Execution failure - break-dbg.exp - GDB for Linux Power
Date: Thu, 26 Jun 2025 17:16:08 +0530 [thread overview]
Message-ID: <f20dc233-c9ed-4efc-9efd-51c5a2c9f110@linux.ibm.com> (raw)
In-Reply-To: <20250607083255.bEuXf%cel@linux.ibm.com>
Dear Andrew
I am Sachin from IBM and have recently been assigned the responsibility
to monitor and maintain gdb for IBM-powerpc.
It has been noticed that a new test case recently added to GDB
test-suite is getting failed during execution. The case was added in the
commit id 831b11eab51e63fb635f03001398d73dc4d888aa under your name.
=========================
FAIL: gdb.base/break-dbg.exp: catch syscall
commit 831b11eab51e63fb635f03001398d73dc4d888aa
Author: Andrew Burgess <aburgess@redhat.com>
Date: Mon Jun 2 16:05:14 2025 +0100
gdb: prevent assertion after 'set debug breakpoint on'
Turns out that using 'set debug breakpoint on' will trigger an
assertion for 'catch' style breakpoints, e.g.:
(gdb) file /tmp/hello.x
Reading symbols from /tmp/hello.x...
(gdb) catch exec
Catchpoint 1 (exec)
...
=========================
The issue test case name and the system details are specified in the
mail below.
Therefore, I would like to request your attention and bandwidth for
checking the issue.
Regards:
Sachin.
-------- Forwarded Message --------
Subject: GDB for Linux Power - Daily Build System
Date: Sat, 07 Jun 2025 03:32:55 -0500
From: Carl Love [POWER10] <cel@linux.ibm.com>
To: smonga@linux.ibm.com
Driver level: Fedora release 41 (Forty One)
uname -a: Linux ltcd97-lp3.rch.stglabs.ibm.com 6.13.8-200.fc41.ppc64le
#1 SMP Sun Mar 23 04:39:14 UTC 2025 ppc64le GNU/Linux
* gdb
** 64 bit
checkout OK
GIT commit id: 44e3c1c499331332412c1a04a348da2ddf9cf822
build OK
installation OK
31 failures
1 new failures
0 old failures fixed
+FAIL: gdb.base/break-dbg.exp: catch syscall
next parent reply other threads:[~2025-06-26 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250607083255.bEuXf%cel@linux.ibm.com>
2025-06-26 11:46 ` Sachin Monga via Gdb [this message]
2025-06-26 12:36 ` Tom Tromey
2025-07-02 13:35 ` Carl Love via Gdb
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=f20dc233-c9ed-4efc-9efd-51c5a2c9f110@linux.ibm.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=cel@linux.ibm.com \
--cc=saurov.kanti.shyam@ibm.com \
--cc=smonga@linux.ibm.com \
/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