From: Pedro Alves <palves@redhat.com>
To: Josh Stone <jistone@redhat.com>, gdb-patches@sourceware.org
Cc: sergiodj@redhat.com
Subject: Re: [PATCH v3] gdb: Improve syscall entry/return tracking on Linux
Date: Mon, 19 Oct 2015 08:48:00 -0000 [thread overview]
Message-ID: <5624AE48.2060509@redhat.com> (raw)
In-Reply-To: <1445044608-23715-1-git-send-email-jistone@redhat.com>
On 10/17/2015 02:16 AM, Josh Stone wrote:
> gdb/ChangeLog:
>
> 2015-10-16 Josh Stone <jistone@redhat.com>
>
> * linux-nat.c (linux_handle_syscall_trap): Always update entry/
> return state, even when not actively catching syscalls at all.
> (linux_handle_extended_wait): Mark syscall_state like an entry.
> (wait_lwp): Set syscall_state ignored for other traps.
> (linux_nat_filter_event): Likewise.
>
> gdb/testsuite/ChangeLog:
>
> 2015-10-16 Josh Stone <jistone@redhat.com>
>
> * gdb.base/catch-syscall.c: Include <sched.h>.
> (unknown_syscall): New variable.
> (main): Trigger a vfork and an unknown syscall.
> * gdb.base/catch-syscall.exp (vfork_syscalls): New variable.
> (unknown_syscall_number): Likewise.
> (check_call_to_syscall): Accept an optional syscall pattern.
> (check_return_from_syscall): Likewise.
> (check_continue): Likewise.
> (test_catch_syscall_without_args): Check for vfork and ENOSYS.
> (test_catch_syscall_skipping_return): New test toggling off 'catch
> syscall' to step over the syscall return, then toggling back on.
> (test_catch_syscall_mid_vfork): New test turning on 'catch syscall'
> during a PTRACE_EVENT_VFORK stop, in the middle of a vfork syscall.
> (do_syscall_tests): Call test_catch_syscall_without_args and
> test_catch_syscall_mid_vfork.
> (test_catch_syscall_without_args_noxml): Check for vfork and ENOSYS.
> (fill_all_syscalls_numbers): Initialize unknown_syscall_number.
OK. Please push.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-10-19 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 1:22 [PATCH] " Josh Stone
2015-10-09 10:48 ` Pedro Alves
2015-10-09 17:57 ` Josh Stone
2015-10-09 18:09 ` Pedro Alves
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 [this message]
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=5624AE48.2060509@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