[lsb-discuss] [PATCH] [LSB3.1] lts_li18nux2k.l1-3.1.0.1.tgz getwchar 3 fails on fedora take 2 (glibc2.5).
Tsuyoshi Nagata
nagata3333333 at jp.fujitsu.com
Sun Feb 25 23:37:13 PST 2007
Chinen-san,
I only have 2 patches.
Whole another test passed on glibc-2.5-12.ia64.
Thank you very much for applying my patch.
-nagata
Mitsuru Chinen wrote:
> Hi Nagata-san,
>
> I'm Mitsuru Chinen, Sugiyama's colleague.
> Thank you very much for your investigation and patches.
> I confirmed both of your patches are correct.
>
> I added comments on the bugziila, either.
> Could anyone put these patches into the testsuite, please?
>
> Best Regards,
> ----
> Mitsuru Chinen <mitch at linux.vnet.ibm.com>
>
>
> On Fri, 23 Feb 2007 17:10:12 +0900
> Tsuyoshi Nagata <nagata3333333 at jp.fujitsu.com> wrote:
>
>> Hi,
>> I re-write test code patch to solve getwchar()ELSEQ problem.
>>
>> Tsuyoshi Nagata wrote:
>>> To really help you, I must figure out the error condition
>>> and re-write the error test program. But It's hard to me
>>> to read glibc-src. I choice easy way. "SKIP TEST" ;-)
>> title: TEST getwchar test 3 fails on glibc2.5-12
>> Problem:
>> In glibc 2.3 getwchar(3) always return ELSEQ.
>> The test program gets ELSEQ on valid character.
>> The test did not test on invalid characters.
>> In glibc 2.5 getwchar(3) returns OK on wchar, and
>> returns ELSEQ on invalid character.
>> So the test only sees first character in stdin.
>> the test must tangle the stdin stream to invalid
>> character.
>> Solve:
>> seek testfile until getwchar returns WEOF
>> to make the read head move on invalid character.
>>
>> This patch will work on glibc-2.3 and 2.5 well.
>>
>> -Nagata
>>
>
>
More information about the lsb-discuss
mailing list