Hi Guys,

This is related to my previous post. I've found for larger *.asm files (eg over 500KB), fasm is crashing if I attempt to define the stack size for PE64 executables.

(See attached file as example). If I remove the stack size definition, the source file assemblies and the executable runs correctly. However having a stack size of 4K is not adequate for my application?

Additionally, on my XP x64 SP2 PC, when fasm crashes, the original source file is being deleted (I believe is the Win related not fasm related). This does NOT occur on XP SP2 (32bit).

If someone could at least show that I'm either using the stack keyword incorrectly? or confirm the presence of the bug? I would be greatly appreciated.

(In the attached source, about line 80 is the stack size definition for the PE64).

If FASM crashes, it's error for sure, and you are doing it correctly.

For a quick workaround, you can produce 64 bit COFF instead, and link it to executable with linker (that allows specifying default stack size)

Chewy509: your source file is being deleted? :O

Does this happen with the command-line fasm.exe , or the fasmw.exe editor? Sounds pretty nasty.

The source file is being deleted with both fasm.exe and fasmw.exe on XP x64 only. I'm assuming it's a bug within the x64 version of Windows, as it doesn't happen on the 32bit version of Windows XP.

If someone happens to have a running XP x64 box, can you please test it. (It could be some setting on my box).

Thanks for the workaround.

For the moment I'm using a PE header editor (there's heaps on the internet) and just manually modifying the field in the header. It's working ok for now.

Fixed in 1.67.22 (coming later today).

Thanks, how's the studying going?

1.67.21 - source isn't deleted on Server 2003 Enterprise x64 Edition
It took a long time to assemble, though.
1.67.22 - assembles OK! 4 passes, 0.9 seconds, 146944 bytes