...appears to be broken. I've tried different linkers (MS Link, PoLink). MS Link indicates there are references past the end of the object file. PoLink warns of conflicting flags, and doesn't include the .bss segment in the output EXE. (or, it crashes).

When I manually merge the .bss and .data segments - no errors at all.
So, I must have created initial data in .bss segment? NO: does not have any initial data. Nor do other object files. Yet, the segments are tagged differently within the object files.

I haven't tried re-ordering the segments - should that matter?

Is anyone using MS COFF in their projects?

When you are reporting bug, please post FULL source. Otherwise, we can't reproduce the problem.


Me, no problem sofar

I will work to refine the source demonstraighting the problem and post here. Also, will do the same for the OBJ that crashes PoLink.

I forsee the problem is in DATA flag on uninitialized data section.

Here is simple project producing bad exe from polink and only error from mslink. I've included output from builds, but would only have to add paths to batch file to rebuild. (There is an error in MSCOFF.asm, but it isn't the crash of error - just forgot to correct stack after wsprintf.)

asmfan: you was right

I've found where FASM sets the high bit on the section flags byte, and tracing it back to maybe find out why some are not set correctly.

bitRAKE: asmfan already found the problem: you used "data" flag on BSS section. Do you suggest "data" should be used on BSS?

Okay, the syntax error wasn't clear and the COFF example doesn't have a BSS section nor isit explained in the manual. Thanks (...I'm a little dense on the rebound.)