arla 0.20: getcwd & XFS panics

[Brandon S. Allbery KF8NH]

In message <E0zted9-0000Po-00 at chinook.stanford.edu>, Max writes:
+-----
| You (Brandon S. Allbery KF8NH) wrote:
| > In message <E0ztLNz-0000Ys-00 at 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
| > +--->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
+--->8

The source, and therefore the code/data/BSS in the generated object, didn't 
change in any of those versions; so you were "safe" by luck.  Conceivably 
just using a different compiler to build the same source could have caused 
the same result, though.

| this in either INSTALL, README, or NEWS.  Where are these instructions
| that you are referring to?
+--->8

They were in the announcement of the 0.20 version.  If they weren't included 
in the distribution files, that was an oversight on someone's part.

| > | 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).
| > 
| > 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).
+--->8

Hm.  Can you determine exactly which program is producing the symbol error?  
In Red Hat it could be any of:  xinit, Xwrapper, the X server itself, or the 
window manager (which would cause the X server to shut down immediately).

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery at kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery at ece.cmu.edu
carnegie mellon / electrical and computer engineering			 KF8NH
     We are Linux. Resistance is an indication that you missed the point.