Date: Tue, 9 Jan 2001 15:14:30 -0500
Message-Id: <200101092014.PAA12887@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <%4H66.4380$AH6.751294@newsc.telia.net> (mrhellman@telia.com)
Subject: Re: SV: SV: Strange function addresses
References: <3A5A150E DOT E6EE5A6 AT telia DOT com> <200101081952 DOT OAA05184 AT envy DOT delorie DOT com> <hJp66.4149$AH6 DOT 726852 AT newsc DOT telia DOT net> <200101082108 DOT QAA05839 AT envy DOT delorie DOT com> <%4H66.4380$AH6 DOT 751294 AT newsc DOT telia DOT net>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> kernel.com : $(OBJECTS)
>   ld $(OBJECTS) -o kernel.com -oformat binary -Ttext 0x100

Hmmm... Objdump might be able to disassemble this if you also tell
objdump that it's binary, and convince it to disassemble it.

Try 
objdump -m i386 -b binary -D kernel.com

BUT beware that you can't just create a 32-bit COM file and expect dos
to know what to do with it, if that's what you're trying to
accomplish.  DJGPP tools produce 32-bit programs, and you *need* a
stub for DOS to be able to run it.