From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <hui_zhu@mentor.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw) (timeout) with Linux 2.6.32 and older version
Date: Wed, 04 Jun 2014 16:11:00 -0000 [thread overview]
Message-ID: <538F4522.9050509@redhat.com> (raw)
In-Reply-To: <538EDC2D.8050002@mentor.com>
On 06/04/2014 09:43 AM, Hui Zhu wrote:
> On 05/29/14 03:19, Pedro Alves wrote:
>> And I think we should disable all ptrace options in the child
>> before stepping it, in case some event is reported right
>> at that point, and we mishandle it. Otherwise we'd need to
>> make sure we didn't get an extended wait status before passing
>> it on. But disabling events is just safer.
>
> Could you give me some help on this part?
> I don't know how to disable all ptrace options.
There's a linux_enable_event_reporting function in common/linux-ptrace.c.
Add a linux_disable_event_reporting counterpart, and call that.
--
Pedro Alves
next prev parent reply other threads:[~2014-06-04 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 8:12 Hui Zhu
2014-05-28 19:19 ` Pedro Alves
2014-06-04 8:43 ` Hui Zhu
2014-06-04 16:11 ` Pedro Alves [this message]
2014-06-05 7:48 ` Hui Zhu
2014-06-05 8:43 ` Pedro Alves
2014-06-08 11:16 ` Hui Zhu
2014-06-09 13:58 ` [pushed] Fix a bunch of fork related regressions. (was: Re: [PATCH] Fix gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw) (timeout) with Linux 2.6.32 and older version) Pedro Alves
2014-07-03 16:24 ` [PATCH] Fix gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw) (timeout) with Linux 2.6.32 and older version Hui Zhu
2014-07-04 17:51 ` [PATCH] Handle signals sent to a fork/vfork child before it has a chance to first run (Re: [PATCH] Fix gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw) (timeout) with Linux 2.6.32 and older version) Pedro Alves
2014-07-05 6:08 ` Hui Zhu
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=538F4522.9050509@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).