From owner-freebsd-current Sat Nov 6 10:42: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 00B0714E82 for ; Sat, 6 Nov 1999 10:41:59 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA11324; Sat, 6 Nov 1999 12:41:58 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id MAA29996; Sat, 6 Nov 1999 12:41:58 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id MAA26019; Sat, 6 Nov 1999 12:41:57 -0600 (CST) Date: Sat, 6 Nov 1999 12:41:57 -0600 (CST) From: Jonathan Lemon Message-Id: <199911061841.MAA26019@free.pcs> To: jhay@mikom.csir.co.za, current@freebsd.org Subject: Re: doscmd broken on current? X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Is doscmd working for anyone on current? Here I just get: > >--------- > >I have tried it on a single processor and SMP -current and both do the same >thing. I had it working a while back, so I think my configuration is ok. > >Ideas on how to look into this? Start by invoking it with the various debug/trace options. I'd guess that it may be broken by the signal-related changes that were made recently. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message