Re: [PATCH] Make environ.exp run on all platforms (and create info-program.exp)

[Luis Machado <lgustavo@codesourcery.com>]

On 04/13/2017 01:34 PM, Sergio Durigan Junior wrote:
> On Thursday, April 13 2017, Luis Machado wrote:
>
>>>> If you don't have access to bare-metal testing, i could give this a
>>>> try (it may take a couple days though) and report back.
>>>
>>> I don't think I have access to a bare-metal easily; if you could test
>>> this, I'd really appreciate.
>>
>> Got it. I'll let you know what i see (likely next week).
>
> Thanks, much appreciated!
>

Sorry for the delay. Here it is, for aarch64 bare-metal (both hardware 
and qemu):

--

                 === gdb Summary ===

# of expected passes            19
# of unexpected failures        4


Running /gdb/testsuite/gdb.base/info-program.exp ...
FAIL: gdb.base/info-program.exp: info program after run to main
FAIL: gdb.base/info-program.exp: info program after next
FAIL: gdb.base/info-program.exp: info program after deleting all breakpoints

Running /gdb/testsuite/gdb.base/environ.exp ...
FAIL: gdb.base/environ.exp: show environment works

--

The failure for environ.exp seems harmless. I can see the environment 
variables being printed, but something in the pattern matching is off. I 
have a number of environment variables, but the matching still fails. I 
can try to see if there is anything obvious if it doesn't ring any bells 
for you.

For info-program, these failures seem to be related to the "info 
program" output our remote target provides:

--

Breakpoint 1, main (argc=0, argv=0x0) at 
/gdb/testsuite/gdb.base/normal.c:23^M
23        return 0;^M
(gdb) info program^M
Debugging a target over a serial line.^M
Program stopped at 0x80000a28.^M
It stopped at breakpoint 1.^M
Type "info stack" or "info registers" for more information.^M
(gdb) FAIL: gdb.base/info-program.exp: info program after run to main
next^M
24      }^M
(gdb) PASS: gdb.base/info-program.exp: advancing pc
info program^M
Debugging a target over a serial line.^M
Program stopped at 0x80000a2c.^M
It stopped after being stepped.^M
Type "info stack" or "info registers" for more information.^M
(gdb) FAIL: gdb.base/info-program.exp: info program after next

...

(gdb) info breakpoints^M
No breakpoints or watchpoints.^M
(gdb) info program^M
Debugging a target over a serial line.^M
Program stopped at 0x80000a28.^M
It stopped at a breakpoint that has since been deleted.^M
Type "info stack" or "info registers" for more information.^M
(gdb) FAIL: gdb.base/info-program.exp: info program after deleting all 
breakpoints

--

So maybe a matter of making the pattern matching a bit more flexible?

Let me know if you want more information.