This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH, ppc] Fix hw *points for embedded ppc in a threaded environment
- From: Luis Machado <lgustavo at codesourcery dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: "'gdb-patches at sourceware dot org'" <gdb-patches at sourceware dot org>
- Date: Tue, 23 Apr 2013 11:33:47 +0200
- 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>
- Reply-to: lgustavo at codesourcery dot com
Hi,
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.
So the test could work around this by making sure that threads
don't exit until after all watchpoints have been tested.
Thanks for the analysis! I modified the testcase to prevent those
threads from exitting and fixed the weird identation (i messed it up
when copying from another source probably).
But, there still seems to be something odd here. When the number of
threads is greater than the number of available hardware watchpoints,
GDB still seems to miss watchpoint hits.
I'm currently trying to narrow this down.
Luis