From: Daniel Jacobowitz <drow@false.org>
To: Kishore Paul <kishorep@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: gdb remote serial protocol qC and vCont question
Date: Fri, 08 Dec 2006 03:29:00 -0000 [thread overview]
Message-ID: <20061208032856.GA21855@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2006-12-08 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 0:27 Kishore Paul
2006-12-08 1:32 ` Daniel Jacobowitz
[not found] ` <4578CDF7.2000909@freescale.com>
2006-12-08 3:29 ` Daniel Jacobowitz [this message]
2006-12-08 22:00 ` Kishore Paul
2006-12-08 2:35 Kishore Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061208032856.GA21855@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kishorep@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox