All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: scott hutinger <srh@www.mprojects.wiu.edu>
To: Kevin Hendricks <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org,
	scott hutinger <srh@www.mprojects.wiu.edu>
Subject: Re: Bug in glibc 2.1.3 linuxthreads in pthread_cond_timedwait_relative
Date: Fri, 28 Jan 2000 21:10:54 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.3.95.1000128210239.1756B-100000@www.mprojects> (raw)
In-Reply-To: <00012814481500.18396@localhost.localdomain>


Kevin,

Yes!  I would like to keep it in the realm of what people download :-)  So
I don't need to do a build that takes all night on a 8100.

Thanks much, as always, you come through with a fix !!!!

scott

On Fri, 28 Jan 2000, Kevin Hendricks wrote:

> Hi,
>
> If you are using Franz Sirl's glibc 2.1.3 0k or 0l rpms and are seeing funny
> hangs with linuxthreads programs, here is a small patch to fix the problem of
> restarting pthread_cond_timedwait_relative_new with the same timeout and not
> remaining time.
> (see my earlier problem report).
>
> The patch file is attached:
>
> Kevin
>
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-01-29  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.95.1000128103100.276B-100000@www.mprojects>
     [not found] ` <00012814071700.05087@localhost.localdomain>
     [not found]   ` <vtou2jy3t2q.fsf@astra.cs.uni-dortmund.de>
2000-01-28 22:45     ` Bug in glibc 2.1.3 linuxthreads in pthread_cond_timedwait_relative Kevin Hendricks
2000-01-29  3:10       ` scott hutinger [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=Pine.LNX.3.95.1000128210239.1756B-100000@www.mprojects \
    --to=srh@www.mprojects.wiu.edu \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.