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:48:00 -0000 [thread overview]
Message-ID: <200307281948.h6SJmHG01050@magilla.sf.frob.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of Sunday, 27 July 2003 12:17:42 -0400 <20030727161737.GA23676@nevyn.them.org>
> 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.
> 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.
next prev parent reply other threads:[~2003-07-28 19:48 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 [this message]
2003-07-28 19:49 ` Daniel Jacobowitz
2003-07-28 19:54 ` Roland McGrath
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=200307281948.h6SJmHG01050@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