The SASM I.D.E. assembler for NASM, GAS, FASM and MASM.

The SimpleASM named SASM is a simple open source crossplatform IDE for NASM, MASM, GAS, FASM assembly languages and is working with Windows and Linux.
I tested the Windows version 3.8.0 with FASM x64 example and is working well.
Also I tested another FASM files from my projects area and also working great.
You need to add the FASM folder into SASM folder and this just to include all libraries of FASM.
You can use the help page by pressing the F1 key.
Also you need to check from Menu Page the Settings of your build project.
You can download it from here.

Assembly language x64: The System V ABI – part 001.

The System V Application Binary Interface named ABI defines a system interface for compiled application programs.
This System V Application Binary Interface is a set of specifications that detail calling conventions, object file formats, executable file formats, dynamic linking semantics, and much more.
The ABI defines a binary interface for application programs that are compiled for System V implementations on many different hardware architectures.
Also the System V ABI is a family of specifications composed of two basic parts:
– a generic part of the specification ( describes those parts of the interface that remain constant across all hardware implementations of System V;
– a processor-specific part ( the specification describes the parts of the specification that are specific to a particular processor architecture ).
Virtual addresses and file offsets for the 64-bit PowerPC processor family segments are congruent modulo 64
Kbytes (0x10000) or larger powers of 2. Although 4096 bytes is currently the 64-bit PowerPC page size, this
allows files to be suitable for paging even if implementations appear with larger page sizes. The value of the
p_align member of each program header in a shared object file must be 0x10000.
You need to put segments with different characteristics in separate 256 Mbyte portions of the address space, to give the operating system full paging flexibility in the 64-bit address space.
One example of an executable file (the program linked with a base address of 0x10000000):

The possible corresponding program header segments:

The memory image of virtual adress for the program above is shown here, assuming 4096 (0x1000) byte pages.

Documents about: System V ABI
TODO:Ensure whether these are the latest official links.

New x64dbg debugger released.

Today, January 4, 2017 come with new released version of x64dbg debugger application.
This is a open-source x64/x32 debugger for windows and is under constant active development.
The x64dbg can debug both x64 and x32 applications and used Qt, TitanEngine, capstone, Yara, Scylla, Jansson, lz4, XEDParse, Keystone, asmjit and snowman.
Simple, powerful development this debugger come with many features.
You can download ths application from here.

fasm about format ELF executable 3 – part 002 .

If you read fasm-about-format-elf-executable-3 tutorial then you will have some errors.
It’s just a simple example to show you how to deal with .inc files in your project.
You need to have and files to run fasm with proj.asm.
This tow files will come with date and functions for your project.
First the proj.asm file :

The next two .inc files  …first come with :

and the file come with :

And the result is:

fasm about format ELF executable 3 – part 001 .

The Executable and Linking Format named ELF providing developers with a set of
binary interface definitions that extend across multiple operating environments.

This is one simple example using fasm and ELF executable 3 .

Let’s run it:

Using format ELF executable 3 I can create segment readable executable and use it.

Also this allow me to set the aligned in the memory.

You can come with more infos about this issue.