From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Roland McGrath <roland@redhat.com>,
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 20:00:00 -0000 [thread overview]
Message-ID: <16165.33456.576337.632170@localhost.redhat.com> (raw)
In-Reply-To: <20030728194948.GA25297@nevyn.them.org>
Daniel Jacobowitz writes:
> On Mon, Jul 28, 2003 at 12:48:17PM -0700, Roland McGrath wrote:
> > > I noticed recently, after switching kernels (I'm temporarily running a
> > > Debian system with a Red Hat kernel - don't ask)
> >
> > We won't ask. But, as you might imagine, we do run the gdb test suite on
> > our kernels, and we haven't seen this. So you indeed must have hit upon a
> > lucky combination of hardware and software between that RH kernel and your
> > Debian userland that happens to bite.
>
> 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.
>
No, not usually. I can try though.
elena
> > > Ingo/Roland - might want to export ShdPnd in the RH kernels...
> >
> > We probably will. I always used that patch when debugging the kernel
> > signals code in the past.
>
> Thanks.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-07-28 20:00 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
2003-07-28 20:00 ` Elena Zannoni [this message]
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=16165.33456.576337.632170@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mingo@redhat.com \
--cc=roland@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