Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <46489627.9020508@roguewave.com>
Date: Mon, 14 May 2007 11:02:31 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: unprintable characters in Windows build logs
References: <461F0438.2070700@roguewave.com> <4638B61C.30703@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE64387D838D@epmsa009.minsk.epam.com>
 <4648824D.4060002@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE64387D8476@epmsa009.minsk.epam.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE64387D8476@epmsa009.minsk.epam.com>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 8bit

Farid Zaripov wrote:
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com] 
>> Sent: Monday, May 14, 2007 6:38 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: Re: unprintable characters in Windows build logs
>>
>> Farid Zaripov wrote:
>>>> -----Original Message-----
>>>> From: Martin Sebor [mailto:sebor@roguewave.com]
>>>> Sent: Wednesday, May 02, 2007 7:03 PM
>>>> To: stdcxx-dev@incubator.apache.org
>>>> Subject: Re: unprintable characters in Windows build logs
>>>>
>>>> Hi Farid,
>>>>
>>>> The question mark symbol that shows up in the browser is
>>>> U+FFFD, the Unicode Replacement Character. The actual
>>>> character in the log is the NUL ('\0'). I searched the Windows 
>>>> scripts for where we might be inserting NULs but couldn't find 
>>>> anything. Do you happen to have any idea where it might be coming 
>>>> from? Could the IDE be inserting it?
>>>   That NUL characters has been inserted by IDE (devenv.com) 
>> from MSVC 
>>> 7.1.
>> Yeah, I suspected as much after I found out that the MSVC 8.0 
>> logs are fine (and better formatted, too). Is there an easy 
>> way to get rid of them? Have you seen anything about it on 
>> newsgroups of MSVC discussion forums?
> 
>   I'm afraid the only way to get rid of them is postprocess output using some script.

I see. I'm not sure it's worth the trouble unless we already do
some other preprocessing on these or other files. What do you
think?

> That characters is coming during cleanup step. Windows build scripts doesn't contain
> such step. I suppose that night build system invokes cleanup step after invoking the
> build_msvc-x.x.bat batch file. This batch file invokes build.wsf script and then makelog.wsf
> script. I can add "/clean" swit�h to the build.wsf script and add invoking "build.wsf /clean"
> �fter invoking makelog.wsf within build_msvc-x.x.bat batch file.

I suppose the nightly build script that invokes the Windows
infrastructure could do this type of postprocessing for us
since it already does do some processing (I think it does).
Andrew, what are your thoughts?

FWIW, I don't think this particular issue is a major or even
moderately serious problem, but it seems like eliminating control
characters would make the infrastructure more robust in general.

Martin