[428] in arla-drinkers
Re: arla 0.20: getcwd & XFS panics
daemon@ATHENA.MIT.EDU (Max)
Fri Dec 25 16:30:31 1998
From owner-arla-drinkers@stacken.kth.se Fri Dec 25 21:30:31 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 9928 invoked from network); 25 Dec 1998 21:30:29 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 25 Dec 1998 21:30:29 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id WAA03042
for arla-drinkers-list; Fri, 25 Dec 1998 22:25:32 +0100 (MET)
Received: from assaris.sics.se (assaris.sics.se [193.10.66.108])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id WAA03035
for <arla-drinkers@stacken.kth.se>; Fri, 25 Dec 1998 22:25:27 +0100 (MET)
Received: (from assar@localhost) by assaris.sics.se (8.9.1/8.7.3) id WAA05545; Fri, 25 Dec 1998 22:26:44 +0100 (CET)
Subject: Re: arla 0.20: getcwd & XFS panics
In-Reply-To: <199812250310.WAA32521@rushlight.kf8nh.apk.net> from "Brandon S. Allbery KF8NH" at "Dec 24, 1998 10:10:57 pm"
To: allbery@kf8nh.apk.net (Brandon S. Allbery KF8NH)
Date: Fri, 25 Dec 1998 13:18:43 -0800 (PST)
Cc: arla-drinkers@stacken.kth.se
From: Max <maxk@chinook.stanford.edu>
X-Mailer: ELM [version 2.4ME+ PL50s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E0zted9-0000Po-00@chinook.stanford.edu>
Lines: 48
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
You (Brandon S. Allbery KF8NH) wrote:
> 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.
This was never a problem with the old getcwd, I've been doing this
ever since version 0.14 came out. I also didn't see any mention of
this in either INSTALL, README, or NEWS. Where are these instructions
that you are referring to?
> | 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.
The X server is linked against glibc-2.0.7u (or at least it should
be).
> 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
It produces:
0006a230 T __getcwd
0006a230 W getcwd
Max
