Re: [FYI/pushed v4 03/25] Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THREAD_CLONED

[Pedro Alves <pedro@palves.net>]

Hi!

On 2023-11-14 12:55, Guinevere Larsen wrote:
>>
>> +gdb_test_multiple "catch syscall group:process" "catch process syscalls" {
>> +    -re "The feature \'catch syscall\' is not supported.*\r\n$gdb_prompt $" {
>> +    unsupported $gdb_test_name
>> +    return
>> +    }
>> +    -re ".*$gdb_prompt $" {
>> +    pass $gdb_test_name
>> +    }
>> +}
> In the clang buildbot we're getting this output:
> 
> (gdb) catch syscall group:process
> warning: Can not parse XML syscalls information; XML support was disabled at compile time.
> Unknown syscall group 'process'.
> (gdb) PASS: gdb.threads/stepi-over-clone.exp: catch process syscalls
> 
> This should be a failure, and should likely skip the next few tests.
> 
> I don't know

Meh.  I guess we should make it UNSUPPORTED and bail.  But, really that is just
likely to make us not notice GDB wasn't built with XML support.  There's really no
good reason for that nowadays.  It's not like expat is a complicated dependency.

That buildbot should be fixed to configure gdb with libexpat available, IMO.

Or could it be that expat is supposedly available but it fails to build with Clang?
That would be very surprising, though.