Actually if you are referring to ld.so.conf, yes, it does contain
/usr/X11R6/lib,  /usr/lib, and /usr/pkg/lib entries. And I do get the
message upon boot up that the run time library cache is being created
(ld.so.hints)  If not, I would get an explicit error about a specific
library not being found.   Actually I have finally gotten X up and running
with several Xterms, but it does not work consistently, it seems the longer
the machine has been on, the more prone it is to crashing upon opening X. I
left X open all day, and it was working fine when I got home in the
evening, however I decided to reboot just to see what happened, and sure
enough, it crashed upon opening X.  I think it must be a hardware problem.

Thanks to everyone's input

Stephen Eastman

----------
> From: Gordon W. Ross <gwr@netbsd.org>
> To: Stephen Eastman <seastman@uswest.net>
> Cc: Netbsd Sun3 Mailing list <port-sun3@netbsd.org>
> Subject: Re: X on a 3/80
> Date: Monday, March 22, 1999 8:05 PM
> 
> I bet the cause is this:
> 
> Your xterm file has the setuid bit set, which causes ld.so to
> ignore the LD_LIBRARY_PATH and therefor not find libraries.
> Did you setup ld.conf for ldconfig?  Try "ldd xterm" also.
> 
> Stephen Eastman writes:
>  > Well I'm starting to narrow it down:  It seems that X bombs when I try
to
>  > start it with certain apps including an Xterm.  I can  start and run X
fine
>  > with only xclock and twm running, but these seem to only work if I
have
>  > rebooted _after_ X bombing out from trying to run xterm.  I'm getting
a
>  > feeling that the libraries are loading in memory, are somehow
corrupted by
>  > Xterm or Xcalc (the apps that have bombed so far) and thus I can't
start X 
>  > again, (even after I've removed the offending apps from my xinit
file),
>  > until I reboot. I have seen fragments of errors regarding ld.so, but
they
>  > are broken up and not explicit. I thought initially that  I had bad
>  > libraries or maybe ld.so was bad, but I've  installed the 1.3 as well
as
>  > the 1.3.2 binaries and the same thing happens. I'm wondering if I have
some
>  > bad memory.  How good is the post memory test on a 3/80, will it
actually
>  > tell you if memory is bad?
>  > 
>  > Thanks for all the help
>  > 
>