This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix watch_thread_num testcase for ppc32

From: Luis Machado <luisgpm at linux dot vnet dot ibm dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org
Date: Wed, 09 Jan 2008 10:55:29 -0200
Subject: Re: [patch] Fix watch_thread_num testcase for ppc32
References: <1199849652.22083.20.camel@gargoyle> <20080109041508.GA21281@adacore.com> <1199871500.22083.29.camel@gargoyle> <20080109124806.GC27746@caradoc.them.org>
Reply-to: luisgpm at linux dot vnet dot ibm dot com

> Five threads looping without a CPU delay really messes up interactive
> performance; that's why I reduced the thread count for schedlock.exp
> recently.

Sounds like a good reason to leave the delay there.

> Sounds to me like a bug in GDB, not a problem with the test.

Yes, probably. I believe there is a signal being missed somewhere.

If i use usleep(0) (calls sched_yield), the testcase runs just fine. But
switching to a delay eventually breaks the test.

Any ideas?

-- 
Luis Machado
Software Engineer 
IBM Linux Technology Center

References:
- [patch] Fix watch_thread_num testcase for ppc32
  - From: Luis Machado
- Re: [patch] Fix watch_thread_num testcase for ppc32
  - From: Joel Brobecker
- Re: [patch] Fix watch_thread_num testcase for ppc32
  - From: Luis Machado
- Re: [patch] Fix watch_thread_num testcase for ppc32
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]