Topic created on: December 22, 2007 11:03 CST by cyphunk .

or perhaps a libdasm issue, having dug that far just yet.

Pydasm gives the following Intel ASM which fasm, as, or gcc inline have trouble compiling:
    mov dword [ebp-0x10],0x0

It should(?) be:
    mov dword ptr [ebp-0x10],0x0
or am I missing something?

If I use AT&T ASM libdasm's output compiles fine, inline gcc or otherwise:
    movl $0x0,0xfffffff0(%ebp))

Is there a way to direct libdasm to output the proper ASM?  Or a way to direct gcc inline, as or fasm to handle the issue during compile?