From: Ulrich Drepper <drepper@cygnus.com>
To: Andreas Jaeger <aj@suse.de>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: Solution to my linuxthreads problem
Date: Mon, 20 Dec 1999 23:32:00 -0000 [thread overview]
Message-ID: <m3so0wda5q.fsf@localhost.localnet> (raw)
In-Reply-To: <199912201734.SAA31126@sturm.suse.de>
Andreas Jaeger <aj@suse.de> writes:
> Yesterday I reported a problem with the current glibc when using
> headers from 2.3.33 on a Linux 2.2.13 system. Together with Andreas
> Schwab we've fixed this with the appended patch. The problem is that
> ugetrlimit doesn't exist and therefore errno is set - but errno is not
> initialized yet. The solution is to move the getrlimit call after
> errno has been set.
Thanks, I've applied the patch.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
prev parent reply other threads:[~1999-12-20 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-20 9:34 Andreas Jaeger
1999-12-20 23:32 ` Ulrich Drepper [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=m3so0wda5q.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=aj@suse.de \
--cc=libc-hacker@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).