[mbedmicro/pyOCD] Support GDB range step (#329)

2 views
Skip to first unread message

Hsiangkai

unread,
Aug 11, 2017, 2:56:40 AM8/11/17
to mbedmicro/pyOCD, Subscribed

If target supports range step, GDB will ask for range step by default.
Under range step, GDB will issue 'r start,end' instead of multiple 's'
packets to target stub. It could reduce greatly the traffic between GDB
and target stub, especially step out one line loop.


You can view, comment on, or merge this pull request online at:

  https://github.com/mbedmicro/pyOCD/pull/329

Commit Summary

  • Support GDB range step

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hsiangkai

unread,
Aug 30, 2017, 1:15:41 PM8/30/17
to mbedmicro/pyOCD, Subscribed

I measured the performance difference of range stepping using the test cases in test/gdb_test.py on my local machine.

Without range stepping:
Average single step time: 0.185346150398

With range stepping:
Average single step time: 0.150705850124

Chris Reed

unread,
Apr 23, 2019, 5:07:10 PM4/23/19
to mbedmicro/pyOCD, Subscribed

Closed #329.

Chris Reed

unread,
Apr 23, 2019, 5:07:11 PM4/23/19
to mbedmicro/pyOCD, Subscribed

Closing. These changes were updated and merged in via #626.

Reply all
Reply to author
Forward
0 new messages