This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix watch_thread_num testcase for ppc32
On Wed, Jan 09, 2008 at 07:38:19AM -0200, Luis Machado wrote:
> The test will create a max of five threads, that will keep updating a
> shared variable.
Five threads looping without a CPU delay really messes up interactive
performance; that's why I reduced the thread count for schedlock.exp
recently.
> The reason why it times out is not really clear, i'm still
> investigating. When you hit continue in 32-bit, GDB seems to stand there
> doing something. It occurs from time to time. Sometimes it will stop due
> to the watchpoint, sometimes it will "lock". When you hit ctrl-C, it's
> clear that GDB is still executing the "nanosleep" function. That's what
> pointed me to usleep().
Sounds to me like a bug in GDB, not a problem with the test.
--
Daniel Jacobowitz
CodeSourcery