This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 4/4] 'catch syscall' feature -- Build system, documentation and testcase
- From: Daniel Jacobowitz <drow at false dot org>
- To: Sérgio Durigan Júnior <sergiodj at linux dot vnet dot ibm dot com>
- Cc: Phil Muldoon <pmuldoon at redhat dot com>, gdb-patches at sourceware dot org
- Date: Tue, 4 Nov 2008 10:14:47 -0500
- Subject: Re: [PATCH 4/4] 'catch syscall' feature -- Build system, documentation and testcase
- References: <1225773088.24532.56.camel@miki> <email@example.com> <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.