On Jun 10, 2014, at 5:02 PM, Ken Mandelberg <[email protected]> wrote:
> I'm doing remote gdb deugging to a stub implemented on the target over tcp. SI works and NEXT works well enough skipping over a function call.
>
> What can be very slow is NEXT from one C statement to the next.
>
> When NEXT skips over a function call it implements it by setting a breakpoint at the return address.
>
> When NEXT skips from one C statement to the next, it does it by doing repeated SI's. This forces the target to send back a bunch of state at
> each SI. This is slow and very slow if the C statement actually has a loop in it.
>
> Is there any way around this other than carefully avoiding NEXT in the worst cases and manually setting breakpoints/CONT?
If your stub supports breakpoints, it will take less work for GDB to do the stepping. Basic stepping involves placing break instructions and restoring the content, repeatedly. That’s a lot more round trips but it requires less stub magic.
paul
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.