flat assembler
Message board for the users of flat assembler.
![]() |
Author |
|
pool
..
Last edited by pool on 17 Mar 2013, 12:02; edited 1 time in total |
|||
![]() |
|
asmcoder
[content deleted]
Last edited by asmcoder on 14 Aug 2009, 14:54; edited 1 time in total |
|||
![]() |
|
baldr
pool,
Section names are irrelevant in executable, they're used by linker to combine sections with the same [base] name from different object files (in COFF e.g.) Usually ".bss" section contains only uninitialized data (as in EXAMPLES\DDRAW.ASM you'd mentioned). fasm or linker omits uninitialized trailing bytes from raw section data in resulting executable, thus making it smaller on disk. asmcoder wrote: bss is usually wrong implementation of VirtualSize in COFF. |
|||
![]() |
|
asmcoder
[content deleted]
Last edited by asmcoder on 14 Aug 2009, 14:54; edited 1 time in total |
|||
![]() |
|
baldr
asmcoder,
Code section can be E-only (at least when you don't need to read from/write to it). Merging sections is not an easy effort regarding [un]initialized data. Though they can reside in a single section (I forgot to mention: in Windows, section name does matter, see UPX sources or OLEAUT32.DLL code). And last, but not least: sections in PE executable are made of sections in COFF object files with linker involved. ![]() |
|||
![]() |
|
asmfan
.text: IMAGE_SCN_CNT_CODE | IMAGE_SCN_MEM_EXECUTE | IMAGE_SCN_MEM_READ
Page protection for execution implies read attribute althou read section attr is not necessary for smart (i believe) MS loader. |
|||
![]() |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.