This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFA [PATCH v4] Implement 'catch syscall' for gdbserver (was Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver)
- From: Pedro Alves <palves at redhat dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, gdb-patches at sourceware dot org
- Date: Sat, 05 Oct 2013 10:15:21 +0100
- Subject: Re: RFA [PATCH v4] Implement 'catch syscall' for gdbserver (was Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver)
- Authentication-results: sourceware.org; auth=none
- References: <1379796907 dot 5980 dot 20 dot camel at soleil> <m3bo3ec7cp dot fsf at redhat dot com> <1380467062 dot 3567 dot 52 dot camel at soleil> <524DBA28 dot 3070706 at redhat dot com> <1380837750 dot 2217 dot 104 dot camel at soleil> <524EFB00 dot 90105 at redhat dot com>
Hi,
I don't have time right now for a more elaborate answer, but ...
On 10/04/2013 06:29 PM, Pedro Alves wrote:
>
> Thinking only in terms of multi-process/thread, I'm inclined to ignore the
> "per-process" thing now, and just leave it as gdbserver making catch
> syscall apply to all processes.
I just realized that we really can't do that. The syscall numbers
sent across the wire are the target-specific numbers. Since gdbserver
might well be debugging processes of different gdbarch's simultaneously
(see the multi-arch support patches from a while ago, the tdesc support
in gdbserver, etc.), we can't assume the same syscall array makes sense
for all processes under gdbserver's control.
--
Pedro Alves