diff options
| author | Tim Wiederhake <tim.wiederhake@intel.com> | 2017-05-02 11:35:54 +0200 |
|---|---|---|
| committer | Tim Wiederhake <tim.wiederhake@intel.com> | 2017-05-02 11:35:54 +0200 |
| commit | 913aeadd9d6b8bdea5131b16dc7ede395097656d (patch) | |
| tree | e162888cebec7fc5d93893c493cf0424aa38bc66 /gdb/testsuite/gdb.python | |
| parent | a3be24ad59d683d1b08df28e093739743a7cf256 (diff) | |
| download | gdb-913aeadd9d6b8bdea5131b16dc7ede395097656d.zip gdb-913aeadd9d6b8bdea5131b16dc7ede395097656d.tar.gz gdb-913aeadd9d6b8bdea5131b16dc7ede395097656d.tar.bz2 | |
Python: Introduce gdb.RecordGap class
As discussed here: https://sourceware.org/ml/gdb-patches/2017-04/msg00157.html
A gap is not an instruction and it should not pretend to be one.
gdb.Record.instruction_history is now a list of gdb.RecordInstruction and
gdb.RecordGap objects. This allows the user to deal with Gaps in the record
in a more sane way.
Diffstat (limited to 'gdb/testsuite/gdb.python')
| -rw-r--r-- | gdb/testsuite/gdb.python/py-record-btrace.exp | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.python/py-record-btrace.exp b/gdb/testsuite/gdb.python/py-record-btrace.exp index ecc8bdf..045e63e 100644 --- a/gdb/testsuite/gdb.python/py-record-btrace.exp +++ b/gdb/testsuite/gdb.python/py-record-btrace.exp @@ -81,7 +81,6 @@ with_test_prefix "replay end" { with_test_prefix "instruction " { gdb_test "python print(i.number)" "1" - gdb_test "python print(i.error)" "None" gdb_test "python print(i.sal)" "symbol and line for .*" gdb_test "python print(i.pc)" "$decimal" if { $gdb_py_is_py3k == 0 } { |