Re: [PATCH 6/7] range stepping: test case

Yao Qi
2013-05-15T08:27:22Z

On 05/15/2013 02:32 AM, Pedro Alves wrote:
> I prefer this over the convenience variable hack. If we ever
> make range stepping work on a target !remote, we can switch to
> look at "set debug infrun 1" output or some new "set debug range-step"
> output. I didn't understand your stated reason in v2 for
> switching away from this. If it was that expect buffer
> overflows, v3 has a tweak that likely fixes it.

In our tests, when running tests with a problematic stub supporting
range stepping, the range stepping of the stub falls back to the single
stepping. This will generate a huge number of rsp packets, and the
gdb.log will blow up to several giga-byte. We use convince variable to
avoid this problem. On the other hand, I don't think it is a good idea
to peek the GDB internal states by checking some rsp packets and
personally I prefer the way that GDB is able to expose some internal
states by some means (command "maint" and convince variables, for example).

--
Yao (é½å°§)