From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11001 invoked by alias); 29 Sep 2002 21:46:26 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 10980 invoked from network); 29 Sep 2002 21:46:26 -0000 Received: from unknown (HELO gateway.sf.frob.com) (64.160.54.138) by sources.redhat.com with SMTP; 29 Sep 2002 21:46:26 -0000 Received: from magilla.sf.frob.com (magilla.sf.frob.com [198.49.250.228]) by gateway.sf.frob.com (Postfix) with ESMTP id DC4B2357E; Sun, 29 Sep 2002 14:40:34 -0700 (PDT) Received: (from roland@localhost) by magilla.sf.frob.com (8.11.6/8.11.6) id g8TLeaJ11364; Sun, 29 Sep 2002 14:40:36 -0700 Date: Sun, 29 Sep 2002 14:46:00 -0000 Message-Id: <200209292140.g8TLeaJ11364@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Andreas Jaeger Cc: GNU libc hacker Subject: Re: glibc make check fails... In-Reply-To: Andreas Jaeger's message of Sunday, 29 September 2002 15:22:06 +0200 X-Shopping-List: (1) Fastidious congestion dice (2) Seismic ostentatious compassion (3) Amphibious nougat (4) Pompous docks X-SW-Source: 2002-09/txt/msg00098.txt.bz2 > 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.