This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug rust/20603] New: gdb fails to properly restart a rust test executable
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 13 Sep 2016 04:25:14 +0000
- Subject: [Bug rust/20603] New: gdb fails to properly restart a rust test executable
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20603
Bug ID: 20603
Summary: gdb fails to properly restart a rust test executable
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: rust
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
Target Milestone: ---
This is on x86-64 Fedora 24.
I'm debugging a rust test program built with "cargo test".
I have some breakpoints set.
During debugging I fix a bug and recompile.
Then I re-"run" in gdb.
This ought to work, but doesn't restore my breakpoints.
I'm not sure if this is some generic gdb bug or something
specific to rust (haven't tried other programs).
gdb shows this:
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
`/home/tromey/gdb/gimli/target/debug/gimli-3e606a263c016831' has changed;
re-reading symbols.
Error in re-setting breakpoint 3: Cannot access memory at address
0x5555556037b0
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /home/tromey/gdb/gimli/target/debug/gimli-3e606a263c016831.
Use `info auto-load python-scripts [REGEXP]' to list them.
Starting program: /home/tromey/gdb/gimli/target/debug/gimli-3e606a263c016831
test_eval_arith
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.
--
You are receiving this mail because:
You are on the CC list for the bug.