This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb remote serial protocol qC and vCont question
- From: Daniel Jacobowitz <drow at false dot org>
- To: Kishore Paul <kishorep at freescale dot com>
- Cc: gdb at sourceware dot org
- Date: Thu, 7 Dec 2006 22:28:56 -0500
- Subject: Re: gdb remote serial protocol qC and vCont question
- References: <4578B16D.3090404@freescale.com> <20061208013236.GA18882@nevyn.them.org> <4578CDF7.2000909@freescale.com>
On Thu, Dec 07, 2006 at 08:29:11PM -0600, Kishore Paul wrote:
> Received packet: [vCont;s:1;c] -------------> (1)
> ....
> < thread switch happens to 2 >
> ....
> <receives S05>
> Received packet: [vCont;s:1;c] -------------> (2)*
>
>
> Between the first and second vCont packet the thread-id changes from 1
> to 2 but this information is somehow not getting communicated to gdb.
> The intent of the second vCont is to do a step for thread 2 and c for
> all other threads.
How do you expect GDB to know this if you aren't telling it? It can't
guess!
The thing you're missing is the 'T' response and the "thread:" item in
it.
--
Daniel Jacobowitz
CodeSourcery