From: Pedro Alves <pedro@codesourcery.com>
To: archer@sourceware.org
Cc: Oleg Nesterov <oleg@redhat.com>, utrace-devel@redhat.com
Subject: Re: BUG: gdb && notification packets (Was: gdbstub initial code, v12)
Date: Tue, 05 Oct 2010 18:35:00 -0000 [thread overview]
Message-ID: <201010051935.11751.pedro@codesourcery.com> (raw)
In-Reply-To: <201010051930.38721.pedro@codesourcery.com>
On Tuesday 05 October 2010 19:30:38, Pedro Alves wrote:
> Now, given this, I won't be surprised if you're seeing races
> with ->s, <-OK, ->vCont sequences, as GDB may well be thinking
> that the "OK" is a reply to the vCont.
>
I meant ->s, <-OK, ->vStopped sequences.
--
Pedro Alves
next prev parent reply other threads:[~2010-10-05 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 18:27 gdbstub initial code, v12 Oleg Nesterov
2010-10-04 18:14 ` Oleg Nesterov
2010-10-05 17:31 ` BUG: gdb && notification packets (Was: gdbstub initial code, v12) Oleg Nesterov
2010-10-05 18:30 ` Pedro Alves
2010-10-05 18:35 ` Pedro Alves [this message]
2010-10-06 17:23 ` Oleg Nesterov
2010-10-06 18:32 ` Pedro Alves
2010-10-07 23:03 ` Oleg Nesterov
2010-10-08 0:03 ` Pedro Alves
2010-10-08 0:23 ` Oleg Nesterov
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=201010051935.11751.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=archer@sourceware.org \
--cc=oleg@redhat.com \
--cc=utrace-devel@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).