From owner-freebsd-hackers Tue Feb 27 10:49:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA11849 for hackers-outgoing; Tue, 27 Feb 1996 10:49:40 -0800 (PST) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA11836 for ; Tue, 27 Feb 1996 10:49:35 -0800 (PST) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id UAA03846; Tue, 27 Feb 1996 20:47:13 +0200 Date: Tue, 27 Feb 1996 20:47:13 +0200 (EET) From: Narvi To: "Eric L. Hernes" cc: "Serge A. Babkin" , hackers@freebsd.org Subject: Re: as(1) patch & dis In-Reply-To: <199602271647.KAA04292@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Tue, 27 Feb 1996, Eric L. Hernes wrote: > > > > > > Sad... > > Where will I get the SCO from... > > So I wont see what the drivers do to write my own ones... > > > > Most of the code that you need has already been written, it's part > of gdb. I've wanted to rip the disassembly stuff > out of gdb and make it stand alone, but haven't found the time (or > really needed it that bad, I've got several copies of SCO) > gdb already knows how to parse COFFs, so it shouldn't be too bad. > > 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? Sander > > > -SB > > > > > > > eric. > > -- > erich@lodgenet.com > erich@rrnet.com > >