This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment
- From: Pedro Alves <palves at redhat dot com>
- To: lgustavo at codesourcery dot com
- Cc: "'gdb-patches at sourceware dot org'" <gdb-patches at sourceware dot org>
- Date: Tue, 23 Apr 2013 17:53:36 +0100
- Subject: Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment
- References: <516EC58C dot 5060501 at codesourcery dot com> <51755821 dot 8020907 at codesourcery dot com> <51755A5F dot 3060009 at redhat dot com> <51756D2B dot 5050204 at redhat dot com> <51758960 dot 2090702 at redhat dot com> <51768D08 dot 4090709 at codesourcery dot com>
Whoops, looks like I forgot to paste this bit of the reply
into the other mail.
On 04/23/2013 02:30 PM, Luis Machado wrote:
> On 04/22/2013 09:02 PM, Pedro Alves wrote:
>> I hacked GDB some more, and I have further insight.
>> GDB _is_ to blame. Updated GDB/test hack patch at the bottom.
>> So GDB is to blame. Fixing this, however, would be a different
>> story, and doesn't look that simple.
I found a PR already covering this, btw. breakpoints/10116.
> The question here is how many threads we should spawn. I went with 10 since that is often greater than the number of hardware watchpoints in a target.
Sounds fine to me.