Re: [PATCH] Restrict gdb.base/gcore-relro-pie.exp to native/linux targets

[Luis Machado <lgustavo@codesourcery.com>]

On 02/23/2017 08:24 AM, Pedro Alves wrote:
> On 02/23/2017 02:13 PM, Luis Machado wrote:
>> This particular test doesn't work correctly on aarch64-elf for a couple
>> reasons.
>>
>> First, the test is supposed to crash and bare-metal targets are not always
>> ready to handle such exceptions like Linux does. In our case the board just
>> keeps cycling within an ISR function.
>
> Hmm?  AFAICS, the testcase is generating the core with gdb_gcore_cmd.
> How on earth is that causing this cycling?

I tend to see this particular target stopping later in the source file 
compared to x86. I had an (incorrect) assumption it was dereferencing 
NULL when running to break_here, but it doesn't seem to be the case. It 
stops right at what would cause the crash:

(gdb) b break_here
Breakpoint 2 at 0x80000a20
(gdb) disass break_here
Dump of assembler code for function break_here:
    0x0000000080000a1c <+0>:     mov     x0, #0x0
    0x0000000080000a20 <+4>:     str     wzr, [x0]

It seems something is off with startup code/stack pointer then. Back to 
the drawing board.

I still think it doesn't make much sense to run these tests if we're not 
sure gcore will support them. They may run a few early tests/setup 
tests, but that won't translate into meaningful PASSes. But i'm ok 
keeping it as-is if others think the early test PASSes are useful.