From: Carl Love via Gdb <gdb@sourceware.org>
To: Sachin Monga via Gdb <gdb@sourceware.org>
Cc: saurov.kanti.shyam@ibm.com
Subject: Re: Test Execution failure - break-dbg.exp - GDB for Linux Power
Date: Wed, 2 Jul 2025 06:35:47 -0700 [thread overview]
Message-ID: <ead8a260-84b9-4019-a65f-3f4ca4cd4d11@linux.ibm.com> (raw)
In-Reply-To: <87bjqay91f.fsf@tromey.com>
Sachin:
Just wondering if you have tried to work on giving some more detail for Tom?
We also have a couple of additional failures. Have you looked at them yet?
Carl
On 6/26/25 5:36 AM, Tom Tromey wrote:
> Sachin> FAIL: gdb.base/break-dbg.exp: catch syscall
>
> Sachin> The issue test case name and the system details are specified in the
> Sachin> mail below.
>
> There's not really enough information here to diagnose the problem.
> Normally we'd want at least the "gdb.log" file for the test.
>
> Also it's probably better to file this kind of thing in bugzilla and CC
> the relevant parties there.
>
> thanks,
> Tom
prev parent reply other threads:[~2025-07-02 13:36 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
2025-06-26 12:36 ` Tom Tromey
2025-07-02 13:35 ` Carl Love via Gdb [this message]
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=ead8a260-84b9-4019-a65f-3f4ca4cd4d11@linux.ibm.com \
--to=gdb@sourceware.org \
--cc=cel@linux.ibm.com \
--cc=saurov.kanti.shyam@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