From: Kevin Buettner <kevinb@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] GDB test suite: Add helper for locating core files
Date: Wed, 11 Oct 2017 08:17:00 -0000 [thread overview]
Message-ID: <20171011011733.19b3658c@pinnacle.lan> (raw)
In-Reply-To: <m31smcp3b6.fsf@oc1027705133.ibm.com>
On Mon, 09 Oct 2017 20:46:21 +0200
Andreas Arnez <arnez@linux.vnet.ibm.com> wrote:
> > Instead, several warnings are now printed instead:
> >
> > WARNING: Can not generate core dump on remote target.
>
> These warnings are newly introduced by the patch.
Yes, I saw that.
> 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 ;-)
In the distant past, I used to run the testsuite against resource
constrained linux machines often of a different architecture from the
host I was running the tests from. These machines would run gdbserver
built for that architecture.
Now, I don't recall whether corefile support in the testsuite actually
worked for those targets, but it at least seems possible due to the
various invocations of remote_exec which are present (prior to your
patch).
Do you think you could restore those calls to remote_exec in your
patch? Or do you know for a fact that they do not work?
Kevin
next prev parent reply other threads:[~2017-10-11 8:17 UTC|newest]
Thread overview: 25+ 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
[not found] ` <20171007094545.1bba5c51@pinnacle.lan>
2017-10-09 18:46 ` Andreas Arnez
2017-10-11 8:17 ` Kevin Buettner [this message]
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
[not found] ` <m360bcfo1b.fsf@oc1027705133.ibm.com>
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=20171011011733.19b3658c@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@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