Some command line tools put nulls in output, causing xml parsing errors

[matt.hughes@…]

Running Microsoft Visual Studio .NET 2003 from sh:exec to build a project results in a parser error from expat on the master because VS.NET outputs null characters in some cases. One solution is to elimiate null characters from the output in Command Line?.execute, which the attached patch does.

If other tools can reasonably be expected to have null characters in their output, it may be more appropriate to do this later, such as just before the master parses the message, or just before the slave sends it. It may also be more appropriate to convert nulls to spaces or something else rather than just eliminating them, or encode nulls in XML in a way that expat likes.

[matt.hughes@…]

Simple fix for nulls in command line output

[cmlenz]

Applied a somewhat simpler modification in [339].