aboutsummaryrefslogtreecommitdiff
path: root/ld
diff options
context:
space:
mode:
authorMarkus Metzger <markus.t.metzger@intel.com>2014-05-20 15:53:44 +0200
committerMarkus Metzger <markus.t.metzger@intel.com>2014-06-25 09:59:08 +0200
commitaef929023e3f9c68126564a96431935d35ce032e (patch)
treec9d8b02a2dc87a3f564f32a8d68a3fcd8d8725ee /ld
parent5fff78c4e0d938bb4fc1375792ffae02a134943c (diff)
downloadgdb-aef929023e3f9c68126564a96431935d35ce032e.zip
gdb-aef929023e3f9c68126564a96431935d35ce032e.tar.gz
gdb-aef929023e3f9c68126564a96431935d35ce032e.tar.bz2
btrace: pretend we're not replaying when generating a core file
When generating a core file using the "generate-core-file" command while replaying with the btrace record target, we won't be able to access all registers and all memory. This leads to the following assertion: gdb/regcache.c:1034: internal-error: regcache_raw_supply: Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) FAIL: gdb.btrace/gcore.exp: generate-core-file core (GDB internal error) Resyncing due to internal error. Pretend that we are not replaying while generating a core file. This will forward fetch and store registers as well as xfer memory calls to the target beneath. gdb/ * record-btrace.c (record_btrace_generating_corefile) (record_btrace_prepare_to_generate_core) (record_btrace_done_generating_core): New. (record_btrace_xfer_partial, record_btrace_fetch_registers) (record_btrace_store_registers, record_btrace_prepare_to_store): Forward request when generating a core file. (record_btrace_open): Set record_btrace_generating_corefile to zero. (init_record_btrace_ops): Set to_prepare_to_generate_core and to_done_generating_core. testsuite/ * gdb.btrace/gcore.exp: New.
Diffstat (limited to 'ld')
0 files changed, 0 insertions, 0 deletions