Re: [gdb/testsuite] Fix missing uint8_t in gdb.fortran/logical.exp

Tom de Vries
2020-03-11T12:00:42Z

On 11-03-2020 11:24, Andrew Burgess wrote:
>> [gdb/testsuite] Fix missing uint8_t in gdb.fortran/logical.exp
>>
>> With test-case gdb.fortran/logical.exp, I run into:
>> ...
>> (gdb) PASS: gdb.fortran/logical.exp: var=l: get hexadecimal valueof "&l"
>> set *((uint8_t *) 0x7fffffffd2bc) = 0xff^M
>> No symbol "uint8_t" in current context.^M
>> (gdb) FAIL: gdb.fortran/logical.exp: var=l: byte 0: set contents of byte at offset 0
>> ...
>>
>> Fix this by using the fortran-native type character instead.
>>
>> Tested on x86_64-linux, with gcc 7.5.0 and clang 5.0.2.
>
> I dug into this because, as we discussed on IRC you are seeing
> failures with 7.5, while I am seeing passes with 7.4. For me I was
> getting the symbol from libgfortan. I wonder if it's possible that
> you're linking against an older version of libgfortran, even with a
> newer gcc?
>

Hi Andrew,

Just to confirm:
- I installed all debuginfo packages that my openSUSE system gdb
suggested for the executable, and
- I rebuild gdb with configure flag
--with-separate-debug-dir=/usr/lib/debug

After these two modifications, the test passes for me without the patch.

Thanks,
- Tom