From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <archer-return-2065-listarch-archer=sourceware.org@sourceware.org>
Received: (qmail 23294 invoked by alias); 20 Jul 2010 15:28:41 -0000
Mailing-List: contact archer-help@sourceware.org; run by ezmlm
Sender: <archer@sourceware.org>
Precedence: bulk
List-Post: <mailto:archer@sourceware.org>
List-Help: <mailto:archer-help@sourceware.org>
List-Subscribe: <mailto:archer-subscribe@sourceware.org>
List-Id: <archer.sourceware.org>
Received: (qmail 23285 invoked by uid 22791); 20 Jul 2010 15:28:40 -0000
X-SWARE-Spam-Status: No, hits=-6.6 required=5.0
	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Date: Tue, 20 Jul 2010 15:28:00 -0000
From: Oleg Nesterov <oleg@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: BUG? gdb, non-stop && c -a
Message-ID: <20100720152620.GA22614@redhat.com>
References: <20100718174851.GA15528@redhat.com> <20100716205147.GA26313@redhat.com> <20100719160127.GA13331@host1.dyn.jankratochvil.net> <20100720131615.GA17450@redhat.com> <20100720140136.GA18643@redhat.com> <20100720141155.GA16382@host1.dyn.jankratochvil.net> <20100720144738.GA21427@redhat.com> <20100720150803.GA19023@host1.dyn.jankratochvil.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100720150803.GA19023@host1.dyn.jankratochvil.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-SW-Source: 2010-q3/txt/msg00048.txt.bz2

On 07/20, Jan Kratochvil wrote:
>
> On Tue, 20 Jul 2010 16:47:38 +0200, Oleg Nesterov wrote:
> > On 07/20, Jan Kratochvil wrote:
> > > > this sends "vCont;c:p4745.4746" but not "vCont;c:p4745.-1" as I'd expect.
> > >
> > > Why is this a problem to list all the threads instead of -1?
> >
> > But doesn't list all threads? p4745.4746 is the single thread?
>
> OK, sorry, I am not used to the protocol.
>
> So yes, but it is immediately followed by enxt vCont for the other thread:
> 	Sending packet: $vCont;c:p4a8f.4a90#b1...Packet received: OK
> 	[...]
> 	Sending packet: $vCont;c:p4a8f.4a8f#e6...Packet received: OK
>
>
> > And, in any case, gdbserver resumes only this thread.
>
> It seems to resume both in my case.  We should provide better reproducers
>
> killall -9 threadit gdbserver;~/t/threadit&p=$!;./gdbserver/gdbserver --multi :1234&sleep 0.5;./gdb -nx -ex 'set non-stop on' -ex 'set target-async on' -ex 'set debug remote 1' -ex 'file ~/t/threadit' -ex 'target extended-remote :1234' -ex "attach $p"
> (gdb) c-a
>
> sends vCont twice.

Yes. When I added "set target-async on" as you suggested, gdb sends
vConct twice.

And,

> > So, it is not possible to enter the CLI mode again after "c -a" ?
> > (unless the target hits the bp or something, of course).
>
> CTRL-C BTW works for me;

^C works too.

Thanks!


So, I'll assume "set target-async on" must be always used if I want
to test something in !all-stop mode. Afaics, this has nothing to do
with gdbserver, it only affects the behaviour of gdb itself.

Oleg.