MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite
Quote from: johnsa on May 21, 2012, 03:37:47 PM
I'm starting to look at building up the line number info necessary for debug mode output. As yet I'm not sure what COFF etc requires for this, I'm assuming it needs a line number+address reference for every instruction? As well as line number for symbol definitions (which is already stored in the symbol table). Any thoughts?
The one thing I do want to fix here over ML is that the line number in source of the actual MACRO must be stored (as this annoys me currently) when debugging you can't really step into a macro and there's no reason why not.. it should be much like a proc.
Quote from: Vortex on May 21, 2012, 04:57:49 PM
Did you try to use C run-time malloc function from msvcrt.dll ?
include \masm32\include\masm32rt.inc
include Malloc.inc
.code
start: call MyTest
inkey "bye"
exit
MyTest proc
LOCAL v1, v2, rc:RECT
mov ebx, Malloc(1000000)
invoke lstrcpy, ebx, chr$("Hey, that's more than enough: ")
print ebx
lea eax, rc
sub eax, ebx
print str$(eax), " bytes for your little proggies", 13, 10
ret
MyTest endp
end start
Quote from: xandaz on May 21, 2012, 07:58:59 PMIs there a way to allocate memory that would be common to two different processes?The VirtualAllocEx function allowes to allocate memory in an other process.