milurt
-
Content Count
34 -
Joined
-
Last visited
Posts posted by milurt
-
-
david heffernan,
if it is so important, i wrote, that you can write for i:=1 to
and i sayed the problem is segm:0000^=83; gave a runtime error.
and i wanted to know about paging and segmentation.
lars fosdal,
i meant ballnumber^:=59 if ballnumber=each segm:0000 or segm:0001
gave the runtime error
-
you want to say getmem gives a pointer to segm:0000,
can you not write for i:=1 and accept that the problem is
ballnumber:=59; if ballpointer=each segm:0000 or segm:0001
-
i do not need efficience code. i have the problem that there is a runtime error at segm:0000 and segm:0001
-
i really do not have to write 1000 0s that is 64 bit.
i program in embarcadero 10.3 windows 10
-
var ballnumber:^BYTE;
Begin
GetMem(ballnumber,70000);
For i:=0 to 70000
do begin ballnumber^:=5;ballnumber:=ballnumber+1;
End;
End.at the next SEGM:0000 which will be written is a
runtime error -
if i use getmem's it seems that i need memory paging or segmentation to get the values.
can somebody explain an asm,c,delphi source, that is usable like
number=Pointer1^;
-
thank you.
-
if i click menu-new embarcadero 10.4 creates 32bit, except menu-crossform, but if i load my '.dpr it
changes to 32bit below the menu.
how i can make it 64 or is there a compiler directive like {$APPTYPE 32} ?
memory paging or segmentation
in Windows API
Posted
but i get always the runtime error on ballnumber=segm:0000