Index
> Windows > VirtualAlloc (?) |
| Author |
|
|
mindcooler 14 Sep 2010, 15:58
XP does that at the end of your process' life.
There might be some caveats with calling from and returning to a command prompt? Was there some leaking version of fasm? |
|||
14 Sep 2010, 15:58 |
|
|
bitRAKE 14 Sep 2010, 16:02
Quote: The ExitProcess function automatically releases virtual memory allocations, so it is not necessary to explicitly free the pages when the program terminates through this execution path. |
|||
|
14 Sep 2010, 16:02 |
|
|
ouadji 14 Sep 2010, 16:34
ok, thank you mindcooler, thank you bitRAKE. Quote:
sorry mindcooler, i don't understand this, Your English sentence is too complex for me. _________________ I am not young enough to know everything (Oscar Wilde)-  |
|||
|
14 Sep 2010, 16:34 |
|
|
baldr 14 Sep 2010, 17:14
ouadji,
Look at this from other angle: when process is terminated, its virtual address space is destroyed completely, along with any memory allocations it done. Handles can seem different, but Windows is said to close them too. Windows console version of fasm had slight problems with memory allocation, probably due to race condition. |
|||
|
14 Sep 2010, 17:14 |
|
|
ouadji 14 Sep 2010, 18:47
ok, as a precaution i'll free all memory allocation myself. _________________ I am not young enough to know everything (Oscar Wilde)- |
|||
|
14 Sep 2010, 18:47 |
|
|
baldr 14 Sep 2010, 18:58
ouadji,
Riiight, better be safe than sorry.  |
|||
|
14 Sep 2010, 18:58 |
|
|
ouadji 14 Sep 2010, 20:07
it's fun to learn the English expression. In French we say : "il vaut mieux prévenir que guerir" (it's better prevent than cure) "better be safe than sorry" ... it's fine too.  _________________ I am not young enough to know everything (Oscar Wilde)- |
|||
|
14 Sep 2010, 20:07 |
|
|
edfed 14 Sep 2010, 22:37
[FR] ouaip!
[ENG] yep! english is optimised in size (and speed). then, better for asm  |
|||
|
14 Sep 2010, 22:37 |
|
< Last Thread | Next Thread > |
Forum Rules:
|