From: Roland McGrath <roland@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com, mingo@redhat.com
Subject: Re: FYI: Increase in schedlock.exp failures in LinuxThreads on an RH kernel
Date: Mon, 28 Jul 2003 19:54:00 -0000 [thread overview]
Message-ID: <200307281954.h6SJsjh01078@magilla.sf.frob.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of Monday, 28 July 2003 15:49:48 -0400 <20030728194948.GA25297@nevyn.them.org>
> Have you run a testsuite using LinuxThreads, but the NPTL-aware kernel?
> That should be enough to trigger it, I think. It won't show up in
> NPTL, because the SIGINT will be load balanced and only delivered to
> one of the threads.
We certainly have in the past, and if it's not part of our regular testing
regime then we should make sure that it becomes one. I'll have to check.
next prev parent reply other threads:[~2003-07-28 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 16:17 Daniel Jacobowitz
2003-07-28 19:48 ` Roland McGrath
2003-07-28 19:49 ` Daniel Jacobowitz
2003-07-28 19:54 ` Roland McGrath [this message]
2003-07-28 20:00 ` Elena Zannoni
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=200307281954.h6SJsjh01078@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mingo@redhat.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