Re: [pushed 1/3] [gdb/testsuite] Fix gdb.cp/*.exp for remote host

[Tom de Vries <tdevries@suse.de>]

On 3/22/23 16:05, Simon Marchi wrote:
> 
> 
> On 3/22/23 04:38, Tom de Vries via Gdb-patches wrote:
>> Fix a few test-cases in gdb.cp/*.exp for remote host using new proc
>> include_file.
> 
> Starting with this patch, I see:
> 
>      info variable everywhere^M
>      All variables matching regular expression "everywhere":^M
>      ^M
>      File /home/simark/src/binutils-gdb/gdb/testsuite/gdb.cp/m-static.h:^M
>      8:      const int gnu_obj_4::everywhere;^M
>      (gdb) FAIL: gdb.cp/m-static.exp: info variable everywhere
> 

Hi Simon,

thanks for reporting this.

I don't see this on openSUSE Leap 15.4 and Tumbleweed, but I managed to 
reproduce on Ubuntu 20.04 (though with the readnow board, it disappears 
again).

Anyway, the problem is that I changed the matching to be more strict, 
and that's what we're seeing the effect of.  I'll propose a patch that 
reverts things to the way things were before, with less strict matching.

As for what I'm seeing:
...
(gdb) info variable everywhere^M
All variables matching regular expression "everywhere":^M
^M
File /data/vries/gdb/src/gdb/testsuite/gdb.cp/m-static.h:^M
8:      const int gnu_obj_4::everywhere;^M
^M
File /data/vries/gdb/src/gdb/testsuite/gdb.cp/m-static1.cc:^M
8:      const int gnu_obj_4::everywhere;^M
(gdb) PASS: gdb.cp/m-static.exp: info variable everywhere
...
the combination of line 8 with m-static1.cc doesn't seem to make sense.

I don't know this as a known issue, so I'll file a PR about it.

Thanks,
- Tom