From owner-freebsd-hackers Tue Feb 27 11:57:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18963 for hackers-outgoing; Tue, 27 Feb 1996 11:57:49 -0800 (PST) Received: from bacall.lodgenet.com (mail@[205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA18951 for ; Tue, 27 Feb 1996 11:57:42 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id NAA02640 for ; Tue, 27 Feb 1996 13:51:24 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma002634; Tue Feb 27 13:50:55 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id NAA25391; Tue, 27 Feb 1996 13:29:51 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.3/8.6.12) with SMTP id NAA05125; Tue, 27 Feb 1996 13:42:18 -0600 (CST) Message-Id: <199602271942.NAA05125@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Narvi cc: "Eric L. Hernes" , "Serge A. Babkin" , hackers@freebsd.org Subject: Re: as(1) patch & dis In-reply-to: Your message of "Tue, 27 Feb 1996 20:47:13 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Feb 1996 13:42:18 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org Precedence: bulk > > On Tue, 27 Feb 1996, Eric L. Hernes wrote: > > > > Actually, SCO's dis(CP) from 3.2v4.2 runs as well under ibcs2 as on > > real SCO. Most of the development system does, except for masm, and > > some other programs that need (use) a vm86 call. > > anyone know why SCO's syslog implementation needs vm86? > > > > So I can examine the interior of an object file? Or am I missing something? sorry, there were two different subjects in that paragraph, and I can't tell which one you are refering to, it may be my fault. yes you can (or should be able) to use an SCO gdb to disassemble COFF .o's, there is probably a gdb binary on the net somewhere that will run under ibcs2 and disassemble third party Driver.o's (ftp://sosco.sco.com ??). If you can't, it shouldn't be too tough for a driver hacker to scotch tape together the parts from the gdb distribution to do that. secondly, the vm86 system call is most definitely not needed to examine the interior of an object file, unless you're running it under some sort of emulator/debugging environment. What I was referring to here was the fact that we compiled some simple programs that use syslog() under SCO, which work under SCO. These same programs work fine if recompiled under FBSD. The problem arises when you try to run the SCO binary under ibcs2, you get a kernel message something to the effect of ibcs2 vm86(): unimplemented system call. Now my question is what could SCO possibly be doing that needs vm86 functionality in a syslog() implementation? Am *I* missing something? I'd guess that it's just some antique code that they haven't recompiled in a very long time. It was meant as somewhat of a snied comment. ;) > > Sander > eric. -- erich@lodgenet.com erich@rrnet.com