Last Updated: 2020-07-25 08:11:06 UTC
by Didier Stevens (Version: 1)
I regularly use disassembler ndisasm (part of the NASM project) in diary entries. One of the features I like, is its ability to read data from stdin: I can pipe the output of a command into ndisasm.
I observed a problem with the Windows version that has now been fixed in version 2.15: stdin was used in text mode, while it has to be used in binary mode. One of the effects of this bug on Windows, is that output is truncated after a CTRL-Z (0x1A) byte was received: this is the EOF marker for text files in Windows.
0x1A is no longer a problem now: