Date: Sun, 27 Oct 1996 16:01:23 +0100 From: Jan-Hein Buhrman <jh@tangram.xs4all.nl> To: leisner@sdsp.mc.xerox.com Cc: freebsd-bugs@freebsd.org Subject: Re: xterm problem gone Message-ID: <199610271501.QAA01657@tangram.xs4all.nl> In-Reply-To: <9610262037.AA07416@gnu.sdsp.mc.xerox.com> (leisner@sdsp.mc.xerox.com)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Marty Leisner" <leisner@sdsp.mc.xerox.com> writes: > I obviously didn't get everything I had to get...I untarred enough stuff > to recompile xterm, and the installed xterm started working... > I didn't see a good manifest of what the tar files were, I had to guess... > Obviously there are dependencies. > ------- Forwarded Message > To: freebsd-bugs@freebsd.org > Subject: problem with xterm in 8/1/96 snapshot > Date: Sat, 26 Oct 1996 14:11:43 -0400 > From: "Marty Leisner" <leisner@sdsp.mc.xerox.com> [...] > : leisner@compaq.home;type xterm > xterm is hashed (/usr/X11R6/bin/xterm) > : leisner@compaq.home;xterm > Segmentation fault > Other x tools work (I'm now using rxvt, I suppose I have to recompile > xterm). > Have minimal symbolic information (instead of stripping) will allow > stack backtracing...also why don't I see a core? > (my ulimit -c is unlimited in bash). [ From my 2.1.0 machine: ] bash$ ls -l /usr/X11R6/bin/xterm -rwsr-xr-x 1 root 10 143360 Nov 3 1995 /usr/X11R6/bin/xterm Couldn't really find it easily somewhere in the man pages, but IIRC, set-uid programs don't give you a core image. Regards, -jh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610271501.QAA01657>