From: Luis Gustavo <luis_gustavo@mentor.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Threads inheriting debug state from parent threads
Date: Fri, 03 Aug 2012 13:01:00 -0300 [thread overview]
Message-ID: <501BF5BC.5070209@mentor.com> (raw)
Hi,
I'm actually chasing a problem with GDB and hw watchpoints for embedded
ppc targets.
If a thread X creates thread Y, is it expected that thread Y will
inherit all the debug state from thread X? Including, for example, any
hardware watchpoints/breakpoints that are set in thread X?
Thanks,
Luis
next reply other threads:[~2012-08-03 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 16:01 Luis Gustavo [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-03 15:58 Threads inheriting debug state from parent threads Luis Gustavo
2012-08-03 15:49 Luis Gustavo
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=501BF5BC.5070209@mentor.com \
--to=luis_gustavo@mentor.com \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.