Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Yao Qi'" <yao@codesourcery.com>,
	"'Eli Zaretskii'" <eliz@gnu.org>,
	       <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Run catch-load.exp on Windows
Date: Tue, 17 Sep 2013 18:39:00 -0000	[thread overview]
Message-ID: <8738p3z6md.fsf@fleche.redhat.com> (raw)
In-Reply-To: <33630.1438547254$1379000229@news.gmane.org> (Pierre Muller's	message of "Thu, 12 Sep 2013 17:36:17 +0200")

>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:

Pierre>   I don't get, I always thought that
Pierre> when using remote debugger, the debuggee is cross-compiled
Pierre> on the machine where GDB is run, not on the remote machine where
Pierre> gdbserver is run.
Pierre>   Thus, I always believed that there is no need to copy the
Pierre> source files to the remote machine, as GDB has the sources
Pierre> available.

Pierre>   Are these assumptions wrong?

Not wrong, just incomplete.  There are different kinds of remote
testing, including "remote host", where the compiler and gdb are both
run on the remote, and just dejagnu is run locally.

However, there is some support in the test suite and dejagnu for copying
files over.

Tom


  parent reply	other threads:[~2013-09-17 18:39 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
     [not found]     ` <33630.1438547254$1379000229@news.gmane.org>
2013-09-17 18:39       ` Tom Tromey [this message]
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=8738p3z6md.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    --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