This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v6 3/4] Share fork_inferior et al with gdbserver
- From: Pedro Alves <palves at redhat dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Wed, 7 Jun 2017 22:06:56 +0100
- Subject: Re: [PATCH v6 3/4] Share fork_inferior et al with gdbserver
- Authentication-results: sourceware.org; auth=none
- References: <1482464361-4068-1-git-send-email-sergiodj@redhat.com> <20170504052954.16936-1-sergiodj@redhat.com> <20170504052954.16936-4-sergiodj@redhat.com> <0e95d746-9293-3301-15ed-84d6c4280116@redhat.com> <87poep8zdg.fsf@redhat.com> <f120b388-1979-5857-bd28-33bbaaf21399@redhat.com> <a9efc19d-fb7a-c686-b1ed-654362e55f31@redhat.com> <87shjbo6ko.fsf@redhat.com>
On 06/07/2017 10:01 PM, Sergio Durigan Junior wrote:
>> >
>> > I tried it against v7, and that works. The think to keep
>> > in mind is that these trace_start_error functions
>> > are only called from the fork child, so they're very much
>> > fork-inferior.c related.
> They're actually being used by some -nat.c files on gdb/, and -low.c
> files on gdbserver. But as I said, I'm OK with your suggestion.
Sure, but that's exactly the code that is related to forking
a child, and which runs on the fork child, after it forks,
and before it execs.
It'd never make sense to call those functions on the fork
parent, which is GDB, because they'd cause GDB to exit!
Thanks,
Pedro Alves