From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
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:55:00 -0000 [thread overview]
Message-ID: <1199883329.11932.13.camel@gargoyle.br.ibm.com> (raw)
In-Reply-To: <20080109124806.GC27746@caradoc.them.org>
> 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
next prev parent reply other threads:[~2008-01-09 12:55 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
2008-01-09 12:55 ` Luis Machado [this message]
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=1199883329.11932.13.camel@gargoyle.br.ibm.com \
--to=luisgpm@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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