From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andreas Jaeger <aj@suse.de>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: glibc make check fails...
Date: Sun, 29 Sep 2002 15:00:00 -0000 [thread overview]
Message-ID: <3D9777F7.7090702@redhat.com> (raw)
In-Reply-To: <200209292138.g8TLcoi11349@magilla.sf.frob.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roland McGrath wrote:
> However, this does not explain AJ's crash because he has a build with no
> __NR_set_thread_area. It must be the modify_ldt call failing, for which we
> have no explanation and AFAIK noone else has seen it.
If this happens the system is in deep trouble anyway.
> In principle the modify_ldt call can fail too, and it would be preferable
> to crash in abort as intended rather than crash in the errno access.
> Also I would be happier not having the duplication between tls.h and useldt.h.
The new thread code has all this cleaned up. It's just not worth it to
worry about the old code too much.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9l3f72ijCOnn/RHQRAsefAKDIxY1NFcEWVMHGsGqyeirIngR9ogCgzeI/
j+l8PBeIK3r9tTAKYDLSzvY=
=XJTG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-29 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 3:26 Andreas Jaeger
2002-09-29 3:54 ` Roland McGrath
2002-09-29 4:20 ` Roland McGrath
2002-09-29 6:23 ` Andreas Jaeger
2002-09-29 14:46 ` Roland McGrath
2002-09-30 9:51 ` Andreas Jaeger
2002-09-30 10:03 ` Andreas Jaeger
2002-09-29 10:43 ` Ulrich Drepper
2002-09-29 14:44 ` Roland McGrath
2002-09-29 15:00 ` Ulrich Drepper [this message]
2002-09-29 15:05 ` Roland McGrath
2002-09-29 11:14 ` Ulrich Drepper
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=3D9777F7.7090702@redhat.com \
--to=drepper@redhat.com \
--cc=aj@suse.de \
--cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).