gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp
authorMarcin Kościelnicki <koriakin@0x04.net>
Sat, 5 Mar 2016 13:48:47 +0000 (14:48 +0100)
committerMarcin Kościelnicki <koriakin@0x04.net>
Wed, 9 Mar 2016 17:44:57 +0000 (18:44 +0100)
commit4366d36e467bf81274edccbea026a91188cc67e3
tree585ed80965b28fb6203b18f1b21c0ebc4b298be8
parentcc2c4da8813b980a4e68272bb43583f4af6fe89c
gdb.trace: Use manually-defined start labels in unavailable-dwarf-piece.exp

On powerpc64, foo/bar point to a function descriptor, not to function code.
Since there are no global labels pointing at the actual function code,
let's make our own.

Regression-tested on x86_64.

gdb/testsuite/ChangeLog:

* gdb.trace/unavailable-dwarf-piece.c (foo): Add foo_start_lbl label.
(bar): Add bar_start_lbl label.
* gdb.trace/unavailable-dwarf-piece.exp: Use foo/bar_start_lbl instead
of foo/bar for emitting DWARF and tracing.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.trace/unavailable-dwarf-piece.c
gdb/testsuite/gdb.trace/unavailable-dwarf-piece.exp