From: Pedro Alves <palves@redhat.com>
To: Josh Stone <jistone@redhat.com>, gdb-patches@sourceware.org
Cc: sergiodj@redhat.com
Subject: Re: [PATCH] gdb: Improve syscall entry/return tracking on Linux
Date: Fri, 09 Oct 2015 18:09:00 -0000 [thread overview]
Message-ID: <561802C0.8060902@redhat.com> (raw)
In-Reply-To: <5617FFF8.50905@redhat.com>
On 10/09/2015 06:57 PM, Josh Stone wrote:
> On 10/09/2015 03:48 AM, Pedro Alves wrote:
>> no-mmu / uclinux systems don't have fork. I'm not sure whether
>> fork returns ENOSYS or SYS_fork isn't even defined there.
>> Maybe just switch to vfork so we can keep catch syscall
>> coverage on those systems?
>
> In kernel/fork.c I see that lacking CONFIG_MMU returns EINVAL.
>
> But it appears a few archs don't implement fork/vfork syscalls at all,
> only clone.
Ah, yeah. Even on x86 glibc doesn't really implement fork
with the fork syscall.
> Maybe I should use CLONE_VFORK for broadest coverage?
That does sound the best.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-10-09 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 1:22 Josh Stone
2015-10-09 10:48 ` Pedro Alves
2015-10-09 17:57 ` Josh Stone
2015-10-09 18:09 ` Pedro Alves [this message]
2015-10-09 23:52 ` Josh Stone
2015-10-10 14:46 ` Pedro Alves
2015-10-09 23:53 ` [PATCH v2] " Josh Stone
2015-10-10 14:52 ` Pedro Alves
2015-10-17 1:17 ` [PATCH v3] " Josh Stone
2015-10-19 8:48 ` 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=561802C0.8060902@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jistone@redhat.com \
--cc=sergiodj@redhat.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