This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: remote protocol extension for step out of range
- To: jtc at redback dot com
- Subject: Re: remote protocol extension for step out of range
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Mon, 05 Feb 2001 10:14:17 -0800
- Cc: gdb at sourceware dot cygnus dot com
- References: <5mwvbjj7k8.fsf@jtc.redback.com> <5mvgqw8hpt.fsf@jtc.redback.com> <3A79BFB3.E2C17712@cygnus.com> <5mpuh2unuq.fsf@jtc.redback.com>
"J.T. Conklin" wrote:
> >From the protocol perspective, I don't think it would work any
> differently than stepping or continuing a given task. Currently
> remote_resume() will send a "set thread" packet if the target's
> current thread is different than GDB's. I didn't change this for
> the new packets, so the debug agent will be able to determine what
> thread the step range is for.
If I understand the existing code correctly, you can only do this
step-range thing for a single thread. If something else happens then
that request is dropped on the floor.
For instance, GDB does a step out of range for thread T1. While this is
happening, thread T2 hits a breakpoint so the target stops. The user
then step out of range T2. I suspect that GDB either:
o forgets that it is step out of ranging T1
o reverts to single stepping for T1
the protocol will certainly only allow GDB to step-out-of-range one
thread.
Andrew