This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/21272] New: Missing call to to_can_do_single_step for arm-none-eabi
- From: "elouan dot appere at club-internet dot fr" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 19 Mar 2017 13:30:28 +0000
- Subject: [Bug gdb/21272] New: Missing call to to_can_do_single_step for arm-none-eabi
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21272
Bug ID: 21272
Summary: Missing call to to_can_do_single_step for
arm-none-eabi
Product: gdb
Version: 7.12
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: elouan.appere@club-internet.fr
Target Milestone: ---
Created attachment 9906
--> https://sourceware.org/bugzilla/attachment.cgi?id=9906&action=edit
Logging ouput from GDB (with debug remote and debug target both set to 1)
I'm currently implementing a GDB remote stub on an ARMv6 target
(--target=arm-none-eabi). This stub does _not_ support single-stepping via the
OS or via hardware.
The stub replies
"PacketSize=516;qXfer:features:read+;QThreadEvents+;vContSupported+;swbreak+;QStartNoAckMode+"
to "qSupported", and "vCont;c;C" to "vCont?".
In spite of this, to_target_can_do_single_step is never called, and GDB sends a
vCont packet containing 's', which the remote stub does not support.
Please find enclosed the logging ouput from GDB (with debug remote and debug
target both set to 1).
Any thoughts?
--
You are receiving this mail because:
You are on the CC list for the bug.