From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19199 invoked by alias); 20 Jul 2010 14:49: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 19188 invoked by uid 22791); 20 Jul 2010 14:49:53 -0000 X-SWARE-Spam-Status: No, hits=-6.5 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 14:49:00 -0000 From: Oleg Nesterov To: Jan Kratochvil Cc: archer@sourceware.org Subject: Re: BUG? gdb, non-stop && c -a Message-ID: <20100720144738.GA21427@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100720141155.GA16382@host1.dyn.jankratochvil.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-SW-Source: 2010-q3/txt/msg00045.txt.bz2 On 07/20, Jan Kratochvil wrote: > > On Tue, 20 Jul 2010 16:01:36 +0200, Oleg Nesterov wrote: > > On 07/20, Oleg Nesterov wrote: > > > > > > Using the same test-case, I did > > > > Another oddity. Again, the same test-case but I guess any mt program > > can be used. > > > > (gdb) set non-stop > > non-stop mode should be generally used together with: > (gdb) set target-async on Hmm, thanks... I'll read the docs about target-async. > > 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? And, in any case, gdbserver resumes only this thread. > > Now it sends "vCont;c:p4745.4745" and resumes the main thread. But > > now gdb doesn't react to ^C and "hangs". (no, SIGINT is not blocked). > > CTRL-C is not useful in target-async mode. OK, thanks. So, it is not possible to enter the CLI mode again after "c -a" ? (unless the target hits the bp or something, of course). Oleg.