From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Yao Qi'" <yao@codesourcery.com>, "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Run catch-load.exp on Windows
Date: Thu, 12 Sep 2013 15:36:00 -0000 [thread overview]
Message-ID: <000301ceafcd$d3bbcda0$7b3368e0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <5231A766.8060108@codesourcery.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Yao Qi
> Envoyé : jeudi 12 septembre 2013 13:37
> À : Eli Zaretskii
> Cc : gdb-patches@sourceware.org
> Objet : Re: [PATCH] Run catch-load.exp on Windows
>
> On 09/12/2013 10:44 AM, Eli Zaretskii wrote:
> > Isn't it better to create a new file gdb_dlfcn.h, and move all the
> > portability stuff there?
>
> It makes troubles on remote-host testing, because gdb_dlfcn.h is not
> copied to the remote machine. Dejagnu only copies *.c files to the
> remote host before compilation.
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.
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?
Pierre Muller
next prev parent reply other threads:[~2013-09-12 15:36 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 [this message]
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
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='000301ceafcd$d3bbcda0$7b3368e0$@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