Re: [Clax86list] Disassembler questions
- From: "Benjamin David Lunt" <spamtrap@xxxxxxxxxx>
- Date: Sat, 26 Jul 2008 14:10:22 -0700
"Charles Crayne" <spamtrap@xxxxxxxxxx> wrote in message
news:20080726135830.39e8d8d6@xxxxxxxxxxxxxxxxxx
On Sat, 26 Jul 2008 12:58:07 -0700
"Benjamin David Lunt" <spamtrap@xxxxxxxxxx> wrote:
The code looks like Linux, but the int 21h looks like DOS.
I haven't done any Linux programming, so I may be wrong here,
but shouldn't the int 21h be int 80h?
Indeed it should.
Most likely, nasm is adding padding to the end of the section. I
don't know much about nasm, but this would be my guess
NASM itself adds an ELF header before the user code, and a lot of
system information following it, but it does not pad out the section(s).
However, if one is disassembling the executable module, then one must
also consider what the linker has done.
Thanks Chuck,
I knew that. I have been working too much with binary only
assembly modules. I haven't used a linker with my assembly
in years. :-)
Thanks,
Ben
.
- References:
- Disassembler questions
- From: thiesd
- Re: Disassembler questions
- From: Benjamin David Lunt
- Re: [Clax86list] Disassembler questions
- From: Charles Crayne
- Disassembler questions
- Prev by Date: Re: [Clax86list] Disassembler questions
- Next by Date: Re: [Clax86list] Atomic operations in 32 and 64 bit platforms
- Previous by thread: Re: [Clax86list] Disassembler questions
- Next by thread: Re: Disassembler questions
- Index(es):
Relevant Pages
|