public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: glibc make check fails...
Date: Sun, 29 Sep 2002 06:23:00 -0000	[thread overview]
Message-ID: <u8d6qxue0x.fsf@gromit.moeb> (raw)
In-Reply-To: <200209291116.g8TBG6U00631@magilla.sf.frob.com> (Roland McGrath's message of "Sun, 29 Sep 2002 04:16:06 -0700")

Roland McGrath <roland@redhat.com> writes:

> Ok, I was wrong.  I actually can only reproduce this in a build that's
> using not 2.4.18 headers but newer headers that define __NR_set_thread_area
> (when running on a 2.4.18 kernel that doesn't have the system call).

My kernel headers do not have that call.

>
> If that is your situation too, are you sure it worked before?  If that is
> not your situation, then I can't reproduce your situation and you will have
> to find some more information for me.
>
> The crash I see is from the useldt.h macros' use of INLINE_SYSCALL
> resulting in it calling __errno_location, which bombs when %gs isn't set up
> yet.  AFAICT the useldt.h macros have the very same issue with errno not
> being set up as the TLS macros have (errno TLS var vs __errno_location
> definition from libpthread, but both need %gs to be set up or they crash).
> So I am going to consolidate those macros and use the versions that avoid
> trying to set errno for both.

Unfortunatly my gdb cannot debug this but it's somewhere in the
libpthread startup code:

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

Without the --enable-kernel=2.4.18 everything works, so it seems to be
a problem with the useldt code,

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-09-29 13:23 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 [this message]
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
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=u8d6qxue0x.fsf@gromit.moeb \
    --to=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).