From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: write and kill in dl-tls.c
Date: Thu, 02 May 2002 22:10:00 -0000 [thread overview]
Message-ID: <1020402397.32336.278.camel@akkadia.org> (raw)
In-Reply-To: <20020502223226.C176C1BA18@perdition.linnaean.org>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Thu, 2002-05-02 at 15:32, Roland McGrath wrote:
> It seems improper that dl-tls.c:oom uses __libc_write and __kill and
> __getpid. Why not just use _dl_fatal_printf? At the very least, use raise
> instead of kill.
Well, I wanted to implement it similar to what the other implementations
do. But it's not really necessary. _dl_fatal_printf should work fine.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-05-03 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 15:32 Roland McGrath
2002-05-02 22:10 ` Ulrich Drepper [this message]
2002-05-03 1:02 ` Roland McGrath
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=1020402397.32336.278.camel@akkadia.org \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@frob.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).