From: Roland McGrath <roland@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: glibc make check fails...
Date: Sun, 29 Sep 2002 14:46:00 -0000 [thread overview]
Message-ID: <200209292140.g8TLeaJ11364@magilla.sf.frob.com> (raw)
In-Reply-To: Andreas Jaeger's message of Sunday, 29 September 2002 15:22:06 +0200 <u8d6qxue0x.fsf@gromit.moeb>
> My kernel headers do not have that call.
Then it is very mysterious!
> Unfortunatly my gdb cannot debug this but it's somewhere in the
> libpthread startup code:
Do you get a core dump you can look at?
> 22306: calling init: /builds/test-install/lib/libpthread.so.0
> 22306:
> 22306: symbol=__errno_location; lookup in file=linuxthreads/ex3
> 22306: symbol=__errno_location; lookup in file=/builds/test-install/lib/libpthread.so.0
> 22306: binding file /builds/test-install/lib/libpthread.so.0 to /builds/test-install/lib/libpthread.so.0: normal symbol `__errno_location' [GLIBC_2.0]
> Segmentation fault
That looks exactly like the failure you'd expect if the set_thread_area
call (via INLINE_SYSCALL) or the modify_ldt call had failed. Since you
don't have set_thread_area, it must be modify_ldt but I don't think anyone
else has seen that fail.
next prev parent reply other threads:[~2002-09-29 21:46 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 [this message]
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
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=200209292140.g8TLeaJ11364@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=aj@suse.de \
--cc=libc-hacker@sources.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).