From: Yao Qi <yao@codesourcery.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Support for HWbreak/watchpoint accross fork/vfork on arm-native
Date: Sat, 08 Feb 2014 00:49:00 -0000 [thread overview]
Message-ID: <52F57EA2.20908@codesourcery.com> (raw)
In-Reply-To: <52EAD0DC.506@linaro.org>
On 01/31/2014 06:23 AM, Omair Javaid wrote:
> This patch updates arm native support for hardware breakpoints and watchpoints
> to accommodate watchpoint/breakpoints across fork/vfork. Previously for arm
> native a record of breakpoints at thread level was being kept which has been
> changed to a process level record to come in sync with gdb-linux calls to
> threads and process creation/destruction hooks.
Is it possible to write a test case which fails before the patch applies
but passes after?
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-02-08 0:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 22:12 Omair Javaid
2014-01-30 22:23 ` Omair Javaid
2014-02-07 15:32 ` Pedro Alves
2014-02-08 0:49 ` Yao Qi [this message]
2014-02-12 15:40 ` Omair Javaid
2014-02-13 5:05 ` Yao Qi
2014-02-13 18:40 ` Pedro Alves
2014-02-14 0:06 ` Omair Javaid
2014-03-08 16:29 ` Omair Javaid
2014-03-10 15:13 ` 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=52F57EA2.20908@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=omair.javaid@linaro.org \
/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