diff options
| author | Luis Machado <lgustavo@codesourcery.com> | 2017-01-20 13:15:36 -0600 |
|---|---|---|
| committer | Luis Machado <lgustavo@codesourcery.com> | 2017-01-20 13:15:36 -0600 |
| commit | d334ae250a3ec888f0603cf8e909d0f425aeb30f (patch) | |
| tree | f96d7f1ef23d1f7a546198b798b11e9c387d44b7 /gdb/lm32-tdep.c | |
| parent | 78cbbba8e0bc8b0288f5ce4360b4689ab893aa13 (diff) | |
| download | gdb-d334ae250a3ec888f0603cf8e909d0f425aeb30f.zip gdb-d334ae250a3ec888f0603cf8e909d0f425aeb30f.tar.gz gdb-d334ae250a3ec888f0603cf8e909d0f425aeb30f.tar.bz2 | |
Make gdb.python/python.exp more robust
I noticed gdb.python/python.exp failing on aarch64-elf like so:
FAIL: gdb.python/python.exp: Test decode_line func1 line number
This particular test expects the line number for func1 to be 19, hardcoded.
In my aarch64-elf tests gdb thinks func1 is at line 20, making the test fail.
The following patch addresses this by reading the line number information from
GDB and comparing it against the python decoded symtab information.
gdb/testsuite/ChangeLog:
2017-01-20 Luis Machado <lgustavo@codesourcery.com>
* gdb.python/python.exp: Check line number against what GDB thinks
the line number is for func1.
Diffstat (limited to 'gdb/lm32-tdep.c')
0 files changed, 0 insertions, 0 deletions