[426] in arla-drinkers
Re: arla 0.20: getcwd & XFS panics
daemon@ATHENA.MIT.EDU (Brandon S. Allbery KF8NH)
Thu Dec 24 22:16:49 1998
From owner-arla-drinkers@stacken.kth.se Fri Dec 25 03:16:48 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 1871 invoked from network); 25 Dec 1998 03:16:47 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 25 Dec 1998 03:16:47 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id EAA28906
for arla-drinkers-list; Fri, 25 Dec 1998 04:11:14 +0100 (MET)
Received: from hilfy.ece.cmu.edu (root@HILFY.ECE.CMU.EDU [128.2.253.106])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id EAA28902
for <arla-drinkers@stacken.kth.se>; Fri, 25 Dec 1998 04:11:10 +0100 (MET)
Received: from speaker.kf8nh.apk.net (root@ANNEX-1.SLIP.ECE.CMU.EDU [128.2.236.1])
by hilfy.ece.cmu.edu (8.8.8/8.8.8) with ESMTP id WAA26912;
Thu, 24 Dec 1998 22:11:05 -0500 (EST)
Received: from rushlight.kf8nh.apk.net (allbery@rushlight.kf8nh.apk.net [10.9.204.1])
by speaker.kf8nh.apk.net (8.8.7/8.8.7) with ESMTP id WAA13325;
Thu, 24 Dec 1998 22:11:04 -0500
Received: (from allbery@localhost)
by rushlight.kf8nh.apk.net (8.8.7/8.8.7) id WAA32521;
Thu, 24 Dec 1998 22:10:58 -0500
Message-Id: <199812250310.WAA32521@rushlight.kf8nh.apk.net>
X-Mailer: exmh version 2.0.2 2/24/98
To: Max <maxk@chinook.stanford.edu>
cc: arla-drinkers@stacken.kth.se
Subject: Re: arla 0.20: getcwd & XFS panics
In-reply-to: Your message of "Thu, 24 Dec 1998 16:45:47 PST."
<E0ztLNz-0000Ys-00@chinook.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 24 Dec 1998 22:10:57 -0500
From: "Brandon S. Allbery KF8NH" <allbery@kf8nh.apk.net>
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
In message <E0ztLNz-0000Ys-00@chinook.stanford.edu>, Max writes:
+-----
| I just compiled Arla 0.20 and noticed some major problems. The first
| mistake was copying getcwd.so to /lib. I did this with all the other
| versions with no major problems. My /etc/ld.so.preload has been
| modified appropriately. As soon as I overwrote the old getcwd.so, the
| system started responding to EVERY command with "Segmentation fault".
+--->8
You didn't pay attention to the instructions, then. Overwriting a shared
library that's in use is fatal in Linux; the install instructions in the
announcement specifically stated that you need to rename the existing
getcwd.so, then copy the new one in, so the running copy isn't overwritten.
| log in and remove getcwd.so from ld.so.preload. Until I did that, I
| couldn't start X (it complained about a missing __getcwd symbol).
+--->8
Is your X server (or wrapper) linked against glibc2/libc6 or libc5? If
glibc2, what version? In glibc-2.0.x, __getcwd is the real getcwd() call;
getcwd is a weak symbol, so that it can be redefined in exactly the way the
replacement getcwd.so does while leaving the original available. Or should
be. It's working here (Red Hat 5.2, glibc-2.0.7) but I have no Debian
systems to compare against.
What does "nm --defined-only --dynamic /lib/libc.so.6 | grep getcwd" print?
It should be something like:
3@rushlight:1002 B$ nm --defined-only --dynamic /lib/libc.so.6 | grep getcwd
00069230 T __getcwd
00069230 W getcwd
(If the program that's failing is linked against libc5, all bets are off.)
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.
