Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Oct 2000 12:10:33 +0300 (EET DST)
From:      jau@iki.fi (Jukka A. Ukkonen)
To:        hackers@freebsd.org
Cc:        christos@zoulas.com
Subject:   tcsh went nuts with FreeBSD-3.5.1 (installed from source code)
Message-ID:  <200010090910.MAA23987@cs94004.pp.htv.fi>

next in thread | raw e-mail | index | archive | help

	Howdy, all!

	I am sending this to hackers@freebsd.org, but I am sending a CC
	to Christos Zoulas, because what I have noticed has an undesired
	effect on tcsh, though apparently this is mostly related to libc
	sources from FreeBSD 3.5.1 release.

	I have seen something very odd happening with tcsh 6.09.00 and
	FreeBSD 3.5.1. Tcsh binary stopped working quite suddenly when I
	installed reeBSD-3.5.1 from source code. It seems to get stuck
	within sigpause() and never comes back among the living again.
	When this happens ps shows me this

		18318  p0  S      0:00.04 -/tcsh
		18319  p0  Z+     0:00.00  (stty)

	So, apparently SIGCHLD does not get through to the shell. For all
	I can tell it seems tcsh should be waiting for one in pjwait() in
	source file sh.proc.c. Re-compiling tcsh static or dynamic makes
	no difference, if libc is compiled from 3.5.1 sources.

	I didn't think the two FreeBSD versions should have so different
	libraries, but it seems to be the case. If I use the old 3.4 libc,
	tcsh is just fine also with FreeBSD-3.5.1 kernel quite independent
	of whether I compile libc locally or not.
	When I try with the locally compiled 3.5.1 libc, it makes no
	difference whether the kernel is 3.5.1 or 3.4. With either kernel
	tcsh gets stuck.
	Do you have any idea what might be going on? Has FreeBSD changed
	the implementation of sigpause() et al. somehow such that the new
	versions somehow conflict with the old version? Or is this some
	sort of glitch in tcsh signals management?

	Quite frankly I assume the problem is only present in the libc
	sources of the 3.5.1 distribution. The problem does not seem to be
	present in the binary version of libc which is distributed as part
	of the 3.5.1 package.

	Has anyone else noticed similar odd problems?
	Does anyone out there have good suggestions about what to try next?
	Fixed 3.5.1 libc source code maybe?


	Cheers,
		// jau
.---  ..-  -.-  -.-  .-    .-  .-.-.-    ..-  -.-  -.-  ---  -.  .  -.
  /    Jukka A. Ukkonen,                          SysOpen Plc, Finland
 /__   M.Sc. (sw-eng & cs)                   (Phone) +358-424-2020-331
   /   Internet: Jukka.Ukkonen@SysOpen.Fi      (Fax) +358-424-2020-700
  /    Internet: ukkonen@nic.funet.fi       (Mobile) +358-400-606-671
 v     Internet: jau@iki.fi               (Home&Fax) +358-9-6215-280


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010090910.MAA23987>