Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix watch_thread_num testcase for ppc32
Date: Wed, 09 Jan 2008 12:48:00 -0000	[thread overview]
Message-ID: <20080109124806.GC27746@caradoc.them.org> (raw)
In-Reply-To: <1199871500.22083.29.camel@gargoyle>

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


  reply	other threads:[~2008-01-09 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  3:34 Luis Machado
2008-01-09  4:15 ` Joel Brobecker
2008-01-09  9:39   ` Luis Machado
2008-01-09 12:48     ` Daniel Jacobowitz [this message]
2008-01-09 12:55       ` Luis Machado
2008-01-09 10:05 ` Andreas Schwab
2008-01-09 11:07   ` Luis Machado

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=20080109124806.GC27746@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.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