Re: displaced stepping and remote targets

"taylor, david" <[email protected]> writes:

> Options that come to mind include:
>
> . make the 'how' of displaced stepping user configurable on-the-fly.
>     . options might include auxv, entry-point, user provided address,
>       target provided address (via qSupported maybe)

I am not sure on this...

>
> . have GNU/Linux displaced stepping fallback to entry-point if auxv
>   fails.

GDB got displaced stepping location from entry-point of symbol before,
but it switched to getting entry point from auxv in case that there is
no symbol, here is the patch
https://sourceware.org/ml/gdb-patches/2015-04/msg00341.html

However, looks you are configuring GDB as linux target, but it doesn't
debug a program on linux target, so it is wrong to fix gdb linux things
(displaced stepping location in your case).

You either have to configure your gdb for bare-metal target, as Maciej
suggested (in this way, displaced stepping isn't supported), or teach
your embedded target and your debugging stub behave like a remote linux
target.

-- 
Yao (齐尧)