From: Daniel Jacobowitz <drow@false.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] 'catch syscall' feature -- Build system, documentation and testcase
Date: Tue, 04 Nov 2008 15:16:00 -0000 [thread overview]
Message-ID: <20081104151447.GB32619@caradoc.them.org> (raw)
In-Reply-To: <1225810920.32321.5.camel@miki>
On Tue, Nov 04, 2008 at 01:01:59PM -0200, Sérgio Durigan Júnior wrote:
> > My only other comment is how this would work on remote targets (i.e.
> > remote target is x86, but your host is PPC).
>
> To be completely honest, I still don't know the answer to this question.
> I'd be glad if some good soul could try to answer this, so that I can
> fix things if needed.
Your patch relies on a change to the native file, right? If so, it
will never trigger on remote. In order for it to trigger, we'd need:
- a new remote protocol extension in gdb.texinfo
- remote.c implementation
- gdbserver implementation
It shouldn't be too hard for someone to add it later. So restricting
the tests to native targets would be enough. Search for
[is_remote target] in the testsuite.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-04 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 4:32 Sérgio Durigan Júnior
2008-11-04 8:19 ` Phil Muldoon
2008-11-04 15:03 ` Sérgio Durigan Júnior
2008-11-04 15:16 ` Daniel Jacobowitz [this message]
2008-11-04 15:36 ` Sérgio Durigan Júnior
2008-11-04 15:50 ` Daniel Jacobowitz
2008-11-04 16:33 ` Tom Tromey
2008-11-07 4:03 ` Sérgio Durigan Júnior
2008-11-04 20:03 ` Pedro Alves
2008-11-04 20:33 ` Sérgio Durigan Júnior
2008-11-04 20:47 ` Pedro Alves
2008-11-04 20:54 ` Eli Zaretskii
2008-11-07 3:58 ` Sérgio Durigan Júnior
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=20081104151447.GB32619@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=sergiodj@linux.vnet.ibm.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