From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18945 invoked by alias); 8 Oct 2010 00:03:54 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 18935 invoked by uid 22791); 8 Oct 2010 00:03:53 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Pedro Alves To: Oleg Nesterov Subject: Re: BUG: gdb && notification packets (Was: gdbstub initial code, v12) Date: Fri, 08 Oct 2010 00:03:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.33-29-realtime; KDE/4.4.2; x86_64; ; ) Cc: archer@sourceware.org, utrace-devel@redhat.com References: <20100930182320.GA17475@redhat.com> <201010061932.31628.pedro@codesourcery.com> <20101007225922.GA18085@redhat.com> In-Reply-To: <20101007225922.GA18085@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010080103.43718.pedro@codesourcery.com> X-SW-Source: 2010-q4/txt/msg00009.txt.bz2 On Thursday 07 October 2010 23:59:22, Oleg Nesterov wrote: > Hmm. Not sure I understand this... gdb could issue a series of Hc+c > after s to do "step a thread and resume all others". > > But this doesn't matter. Obviously vCont is better and more handy. Not in all-stop mode. GDB can not send any other command to the stub until the stub returns a stop reply to the first 's'. Remember, there's no vStopped+notifications in the all-stop mode protocol. -- Pedro Alves