ShellPkg: Fix ASCII and UNICODE file pipes.

Fix various errors when piping a UNICODE or ASCII file to a simple shell 
application that reads standard input and writes it to standard output.

1) When the memory file is created by CreateFileInferfaceMem() to capture the 
pipe output, no UNICODE BOM is written to the memory file. Later, when the 
memory file is read by the application using ShellFileHandleReadLine(), the 
function indicates that the file is ASCII because there is no BOM.

2) If the file is piped as ASCII, the ASCII memory image is not correctly 
created by FileInterfaceMemWrite() as each ASCII character is followed by '\0' 
in the image (when the ASCII data is written to the memory image, the file 
position should only be incremented by half the buffer size).

3) ShellFileHandleReadLine() does not read ASCII files correctly (writes to 
Buffer need to be cast as CHAR8*).

4) FileInterfaceMemRead() and FileInterfaceMemWrite() as somewhat hard to read 
and difficult to debug with certain tools due to the typecasting of This. Added 
a local variable (MemFile) of the correct type to these functions and used it 
instead of This.

Enhancement: ShellFileHandleReadLine() now returns EFI_END_OF_FILE when 
appropriate.

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jim Dailey <[email protected]>

(diff files attached)


_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to