Re: Invalid inputs FAILED (input.at:102) on Solaris

Hi Akim,

On November 26, 2020 8:27 am Akim Demaille wrote:
> Hi Martin,
> 
>> Le 25 nov. 2020 à 09:03, Martin Rehak <[email protected]> a écrit :
>> 
>> Hi Akim,
>> 
>> Strange, absolutely same output:
>> 
>> $ printf "\0\n" > /tmp/foo.y
>> $ LC_ALL=C ./src/bison -fcaret /tmp/foo.y >/tmp/foo.log 2>&1
>> ?1$ xxd /tmp/foo.log
>> 00000000: 2f74 6d70 2f66 6f6f 2e79 3a31 2e31 3a20  /tmp/foo.y:1.1: 
>> 00000010: 6572 726f 723a 2069 6e76 616c 6964 2063  error: invalid c
>> 00000020: 6861 7261 6374 6572 3a20 275c 3027 0a20  haracter: '\0'. 
>> 00000030: 2020 2031 207c 2000 0a20 2020 2020 207c     1 | ..      |
>> 00000040: 205e 0a                                   ^.
>> $ perl -p -e 's{([\0\377])}{sprintf "\\x%02x", ord($1)}ge' /tmp/foo.log
>> /tmp/foo.y:1.1: error: invalid character: '\0'
>>    1 | \x00
>>      | ^
> 
> I am confused.  Please run this:
> 
> make check-local TESTSUITEFLAGS='-d 4'
> 
> and wrap a tarball of tests/testsuite.dir/004 and send it.
> 
>> In case you are not happy with debugging this case (and I would 
>> understand it) is there a way how to disable it?

Tarball is attached.

> You could pass '1-3 5-' as a range of tests to run, but so would
> be a pity.  I'd rather nail that one and be able to forget about it :)

That's my preference also.

Thank you for your time
-- 
m.