From owner-freebsd-hackers Tue Feb 27 04:27:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA14539 for hackers-outgoing; Tue, 27 Feb 1996 04:27:32 -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 EAA14480 for ; Tue, 27 Feb 1996 04:26:04 -0800 (PST) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id OAA02817; Tue, 27 Feb 1996 14:16:04 +0200 Date: Tue, 27 Feb 1996 14:16:04 +0200 (EET) From: Narvi To: "Serge A. Babkin" cc: hackers@freebsd.org Subject: Re: as(1) patch & dis In-Reply-To: <199602271145.QAA07983@hq.icb.chel.su> 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, Serge A. Babkin wrote: > > > > > > BTW, for fixing this bug :-) I have written a 386 disassembler. It's alpha > > > quality yet but already useful. I think any people who wants to > > > reengineer some "object-only" BSDi code will find it useful too. So > > > how about to commit it ? > > > > Will it decode only BSDi code? Can it be used to watch the code companies > > sell on their driver diskettes for SCO? > > Indeed it was written to decode FreeBSD code :-) but it decodes BSDi > (at least 1.1) code wery well too. May be it will be able to decode > the Linux code too (with some changes?). SCO drivers can be easily disassembled > by dis under SCO. Really, dis is braindamaged and I use dumps of > symbol and relocation tables (dis from SCO5 is even more braindamaged, > it disassembles some jump addresses wrong). My dis386 for FreeBSD analyses > them automatically. So may be some day I would write a COFF version of it. > Sad... Where will I get the SCO from... So I wont see what the drivers do to write my own ones... > -SB >