From: anonymous c. <nas...@us...> - 2010-10-13 04:15:46
|
> The .asm file is generated by the makefile just before invoking nasm > ... > Yeah, but in this case it IS the exact same .asm file and nasm binary > that failed a few seconds or minutes before, which makes me wonder > what could induce nasm to behave differently. Does your build system ensure serialization between the Perl script that generates the .asm file and the invocation of the NASM binary? Another possibility is bad buffering, i.e. NASM invoked immediately may see a partial .asm file (not from disk, but a memory buffer), but NASM invoked a little later may see the proper .asm file (from disk). You could try to replace the NASM binary with e.g. cat, to show the content of the .asm file. Though... if that doesn't show a partial .asm file, then you might need to "work your way backwards" by building a custom NASM binary that prints out every input line. (Of course that might change buffering enough to hide/avoid the problem.) |