Date: Sun, 07 Nov 1999 01:03:02 -0800 From: Mike Smith <mike@smith.net.au> To: John Hay <jhay@mikom.csir.co.za> Cc: jlemon@americantv.com (Jonathan Lemon), current@FreeBSD.ORG Subject: Re: doscmd broken on current? Message-ID: <199911070903.BAA10454@dingo.cdrom.com> In-Reply-To: Your message of "Sat, 06 Nov 1999 22:24:35 %2B0200." <199911062024.WAA41602@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911070903.BAA10454>