From owner-freebsd-current Sun Nov 7 1:12:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles510.castles.com [208.214.165.74]) by hub.freebsd.org (Postfix) with ESMTP id 88AB414FBB for ; Sun, 7 Nov 1999 01:12:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA10454; Sun, 7 Nov 1999 01:03:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911070903.BAA10454@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay Cc: jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG Subject: Re: doscmd broken on current? In-reply-to: Your message of "Sat, 06 Nov 1999 22:24:35 +0200." <199911062024.WAA41602@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Nov 1999 01:03:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >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. > > hehehe It dies at the very first vm86 instruction, so I guess something > isn't setup correctly to enter vm86 mode via the sigreturn(): I bet that someone got smart and disallowed PSL_VM in eflags on a return to user-mode. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message