Date: Tue, 27 Feb 1996 14:16:04 +0200 (EET) From: Narvi <narvi@haldjas.folklore.ee> To: "Serge A. Babkin" <babkin@hq.icb.chel.su> Cc: hackers@freebsd.org Subject: Re: as(1) patch & dis Message-ID: <Pine.BSF.3.91.960227141356.2801A-100000@haldjas.folklore.ee> In-Reply-To: <199602271145.QAA07983@hq.icb.chel.su>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960227141356.2801A-100000>