Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Yao Qi'" <yao@codesourcery.com>
Cc: "'Eli Zaretskii'" <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Run catch-load.exp on Windows
Date: Mon, 16 Sep 2013 16:24:00 -0000	[thread overview]
Message-ID: <000301ceb2f9$23136ec0$693a4c40$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <5237058E.50409@codesourcery.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Yao Qi
> Envoyé : lundi 16 septembre 2013 15:20
> À : Pierre Muller
> Cc : 'Eli Zaretskii'; gdb-patches@sourceware.org
> Objet : Re: [PATCH] Run catch-load.exp on Windows
> 
> On 09/12/2013 11:36 PM, Pierre Muller wrote:
> >    I don't get, I always thought that
> > when using remote debugger, the debuggee is cross-compiled
> > on the machine where GDB is run, not on the remote machine where gdbserver
> is run.
> 
> This is remote-target, not remote-host.  Dejagnu is running on build,
> test case is compiled on host, and executable is running on target.  In
> the case you described, host == build, so the test case is not copied.
> However, in remote-host, host != build, Dejagnu has to copy source file
> to the remote host first, and launch compiler on the remote host to
> compile the test case.  The executable can be run on the same machine or
> a different one.

  So, I think I was confusing GDB's idea of build/host/target
with dejagnu idea, which is not exactly the same.
 
> >    Thus, I always believed that there is no need to copy
> > the source files to the remote machine, as GDB has the sources available.
> >
> >    Are these assumptions wrong?
> 
> Usually, we don't, but in remote-host testing, we have to.
OK, thank you for the explanation.

Pierre Muller


  parent reply	other threads:[~2013-09-16 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  1:00 Yao Qi
2013-09-12  2:44 ` Eli Zaretskii
2013-09-12 11:38   ` Yao Qi
2013-09-12 15:36     ` Pierre Muller
2013-09-16 13:21       ` Yao Qi
2013-09-16 14:26         ` Pedro Alves
2013-09-16 16:24         ` Pierre Muller [this message]
     [not found]     ` <33630.1438547254$1379000229@news.gmane.org>
2013-09-17 18:39       ` Tom Tromey
2013-09-16 14:22 ` 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='000301ceb2f9$23136ec0$693a4c40$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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