From owner-freebsd-current@FreeBSD.ORG Wed Oct 2 21:30:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 08A12CD3 for ; Wed, 2 Oct 2013 21:30:55 +0000 (UTC) (envelope-from rodrigo@bebik.net) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [IPv6:2a01:e0c:1:1599::13]) by mx1.freebsd.org (Postfix) with ESMTP id 7F1162BA3 for ; Wed, 2 Oct 2013 21:30:52 +0000 (UTC) Received: from oldfaithful.bebik.local (unknown [82.227.164.69]) by smtp4-g21.free.fr (Postfix) with ESMTP id A6BB64C813F for ; Wed, 2 Oct 2013 23:30:47 +0200 (CEST) Received: by oldfaithful.bebik.local (Postfix, from userid 1001) id 4EA1E802612; Wed, 2 Oct 2013 23:21:07 +0200 (CEST) Date: Wed, 2 Oct 2013 23:21:07 +0200 From: Rodrigo OSORIO To: freebsd-current@freebsd.org Subject: issue with shell/pdksh in current (10 alpha 4) Message-ID: <20131002212106.GA1581@oldfaithful.bebik.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Oct 2013 21:30:55 -0000 Hi, I'm working in a PR about pdksh in current, and I'm not really able to figure out what's going on. So that's the facts : A breakage was reported in august about pdksh in current (ports/181438). The PR says pdksh hangs after the first command was sent ( run pdks, type 'ls' validate and you are locked) After a lookup on the code and a little debug I found that, in current, after the main process fork to perform the 'ls', the child fall in a zombi state and the father remains waiting for the SIGCHLD signal forever. Of course, in 9-STABLE things works fine. I try to use a pdksh build in 9 in current, and things works fine. I start thinking the problem commes from clang. Before any change I test GCC in current,and bang! dosn't works. Here is a little array explaining my tests. Environments: 10.32 : FreeBSD 10 Alpha 4 x32 10.64 : FreeBSD 10 Alpha 4 AMD64 9.32 : FreeBSD 9-STABLE x32 9.64 : FreeBSD 9-STABLE AMD64 build / run in| 10.32 | 10.64 | 9.32 | 9.64 | ---------------------------------------------- Build w/CLANG |KO |KO | Not tested in native env |v3.3 |v3.3 | ---------------------------------------------- Build w/GCC |KO |KO |all OK in native env |v4.6.3 |v4.2.1 |v4.2.1 ---------------------------------------------- Build w/GCC |OK |OK |all KO(Build in 10) in 9-STABLE 32|v4.2.1 |v4.2.1 |v4.6.3 ---------------------------------------------- So.... If I use a pdks build in its own environement with clang or gcc, pdksh fail. The same tes done in 9 success. If I copy 9-STABLE pdksh builds to 10, the imported pdksh works fine. If I copy the 10 pdksh builds to 9, pdksh dosn't works. It seems the problem is related to the build environement in current, without regads to the copiler used. Maybe a macro failure...... Anyone has a clue ? Best regards, - rodrigo