From: Sergio Durigan Junior <sergiodj@redhat.com>
To: lgustavo@codesourcery.com
Cc: "'gdb-patches\@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment
Date: Thu, 18 Apr 2013 00:19:00 -0000 [thread overview]
Message-ID: <m3zjwxay13.fsf@redhat.com> (raw)
In-Reply-To: <516EC58C.5060501@codesourcery.com> (Luis Machado's message of "Wed, 17 Apr 2013 17:53:48 +0200")
Hey!
Thank for the patch. One thing I noticed:
On Wednesday, April 17 2013, Luis Machado wrote:
> Index: gdb-head/gdb/ppc-linux-nat.c
> ===================================================================
> --- gdb-head.orig/gdb/ppc-linux-nat.c 2013-04-17 10:24:52.919499117 +0200
> +++ gdb-head/gdb/ppc-linux-nat.c 2013-04-17 11:12:20.731448515 +0200
> @@ -2179,6 +2179,21 @@ ppc_linux_new_thread (struct lwp_info *l
> for (i = 0; i < max_slots_number; i++)
> if (hw_breaks[i].hw_break)
> booke_insert_point (hw_breaks[i].hw_break, tid);
Didn't you forget to delete the previous line? :-)
> + {
> + /* The ppc Linux kernel causes a thread to inherit its parent
> + thread's debug state, and that includes any hardware
> + watchpoints or breakpoints that the parent thread may have set.
> +
> + For this reason, the debug state of the new thread is cleared
> + before trying to replicate any hardware watchpoints or
> + breakpoints contained in other threads. */
> +
> + /* The ppc debug resource accounting is done through "slots".
> + Ask the kernel the deallocate this specific *point's slot. */
> + ptrace (PPC_PTRACE_DELHWDEBUG, tid, 0, hw_breaks[i].slot);
> +
> + booke_insert_point (hw_breaks[i].hw_break, tid);
> + }
--
Sergio
next prev parent reply other threads:[~2013-04-17 17:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 20:33 Luis Machado
2013-04-18 0:19 ` Sergio Durigan Junior [this message]
2013-04-18 0:51 ` Luis Machado
2013-04-22 21:09 ` Luis Machado
2013-04-22 21:09 ` Pedro Alves
2013-04-23 0:05 ` Pedro Alves
2013-04-23 1:15 ` Pedro Alves
2013-04-23 20:25 ` Luis Machado
2013-04-23 23:18 ` Luis Machado
2013-04-24 3:19 ` Pedro Alves
2013-04-24 6:28 ` Luis Machado
2013-04-24 19:04 ` Pedro Alves
2013-04-25 14:13 ` Luis Machado
2013-05-07 7:44 ` Luis Machado
2013-04-24 4:36 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2012-08-06 14:33 Luis Gustavo
2012-08-06 18:40 ` Jan Kratochvil
2012-08-06 19:02 ` Luis Gustavo
2012-08-06 20:28 ` Jan Kratochvil
2012-08-07 14:55 ` Luis Gustavo
2012-08-07 15:00 ` Jan Kratochvil
2012-08-07 15:02 ` Luis Gustavo
2012-12-27 19:50 ` Luis Machado
2013-01-22 12:12 ` 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=m3zjwxay13.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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