From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] GDB test suite: Add helper for locating core files
Date: Mon, 09 Oct 2017 18:46:00 -0000 [thread overview]
Message-ID: <m31smcp3b6.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <20171007094545.1bba5c51@pinnacle.lan> (Kevin Buettner's message of "Sat, 7 Oct 2017 09:45:45 -0700")
On Sat, Oct 07 2017, Kevin Buettner wrote:
[...]
> E.g. when I test your patch on my x86-64 linux box using the
> following command...
>
> make check RUNTESTFLAGS="--target_board=native-gdbserver"
>
> ...I see 32 fewer passes than before and also one more known failure.
>
> Here are the passes that no longer occur when using your patch:
[...]
> Instead, several warnings are now printed instead:
>
> WARNING: Can not generate core dump on remote target.
These warnings are newly introduced by the patch. They are meant to
improve diagnostics when someone attempts to run the tests on a "real"
remote target. I wanted to clearly document the fact that this is
unsupported (and always was). Also, by documenting this restriction,
maybe someone feels encouraged to lift it ;-)
But it seems I went overboard, now also bailing out in case of
native-gdbserver, which is unnecessary, since no extra handling is
required for that.
How to fix this, though? Rather than bailing out on "is_remote target",
maybe we should check for "isnative" instead? See the delta-patch
below. This should fix the problem with native-gdbserver and is
probably not worse than before in other scenarios, so maybe it's good
enough. WDYT?
> If you can restore support for handling of remote core files, I'd very
> much like to review this patch again.
Thanks, I'd appreciate that.
--
Andreas
-- >8 --
Subject: [PATCH] Squash into "GDB test suite: Add helper for locating core files"
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 2c5e94d..091933a 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5850,7 +5850,7 @@ proc exec_in_dir {dir command} {
# Return the core file's filename, or "", if none was found.
proc run_and_get_core {binfile {arg ""}} {
- if {[is_remote target]} {
+ if {![isnative]} {
warning "Can not generate core dump on remote target."
return ""
}
@@ -5883,7 +5883,7 @@ proc run_and_get_core {binfile {arg ""}} {
# specified. Return that path name, or "" if no core file was found.
proc find_core {binfile coredir {destcore ""}} {
- if {[is_remote target]} {
+ if {![isnative]} {
warning "Can not access remote core file."
return ""
}
next prev parent reply other threads:[~2017-10-09 18:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 18:42 [PATCH 0/2] GDB test suite: Support targets with systemd-coredump Andreas Arnez
2017-09-18 18:43 ` [PATCH 1/2] GDB test suite: Add helper for locating core files Andreas Arnez
2017-10-07 16:45 ` Kevin Buettner
2017-10-09 18:46 ` Andreas Arnez [this message]
2017-10-11 8:17 ` Kevin Buettner
2017-10-11 14:53 ` Andreas Arnez
2017-10-12 13:47 ` Pedro Alves
2017-10-12 16:48 ` Pedro Alves
2017-10-17 9:22 ` Pedro Alves
2017-10-12 17:00 ` Andreas Arnez
2017-10-13 9:28 ` Maciej W. Rozycki
2017-10-13 10:56 ` Andreas Arnez
2017-10-17 13:58 ` Maciej W. Rozycki
2017-10-17 10:06 ` Pedro Alves
2017-10-17 10:01 ` Pedro Alves
2017-10-17 18:21 ` Maciej W. Rozycki
2017-10-18 11:46 ` Pedro Alves
2017-09-18 18:44 ` [PATCH 2/2] GDB test suite: Get core files on targets with systemd-coredump Andreas Arnez
2017-10-17 10:22 ` Pedro Alves
2017-10-17 17:37 ` Andreas Arnez
2017-10-17 18:09 ` Pedro Alves
2017-10-17 18:14 ` Pedro Alves
2017-10-17 18:17 ` Pedro Alves
2017-10-18 15:56 ` Andreas Arnez
2017-10-19 10:48 ` Pedro Alves
2017-10-23 13:41 ` Andreas Arnez
2017-10-23 14:30 ` Pedro Alves
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=m31smcp3b6.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).