From: Tom Tromey <tom@tromey.com>
To: Sachin Monga via Gdb <gdb@sourceware.org>
Cc: aburgess@redhat.com, Sachin Monga <smonga@linux.ibm.com>,
carl Love <cel@linux.ibm.com>,
saurov.kanti.shyam@ibm.com
Subject: Re: Test Execution failure - break-dbg.exp - GDB for Linux Power
Date: Thu, 26 Jun 2025 06:36:12 -0600 [thread overview]
Message-ID: <87bjqay91f.fsf@tromey.com> (raw)
In-Reply-To: <f20dc233-c9ed-4efc-9efd-51c5a2c9f110@linux.ibm.com> (Sachin Monga via Gdb's message of "Thu, 26 Jun 2025 17:16:08 +0530")
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
next prev parent reply other threads:[~2025-06-26 12:37 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 [this message]
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=87bjqay91f.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=cel@linux.ibm.com \
--cc=gdb@sourceware.org \
--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