From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16817 invoked by alias); 14 Sep 2010 21:30:05 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 16784 invoked by uid 22791); 14 Sep 2010 21:30:04 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: Tom Tromey To: Jan Kratochvil Cc: Oleg Nesterov , Roland McGrath , Kevin Buettner , archer@sourceware.org Subject: Re: gdbstub initial code, v9 References: <20100908191838.GA27120@redhat.com> <20100909152937.GA21586@redhat.com> <20100912225350.6d5ccc12@mesquite.lan> <20100914022003.6989A403E6@magilla.sf.frob.com> <20100914160700.GA20290@redhat.com> <20100914163001.GA591@host1.dyn.jankratochvil.net> Date: Tue, 14 Sep 2010 21:30:00 -0000 In-Reply-To: <20100914163001.GA591@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 14 Sep 2010 18:30:01 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2010-q3/txt/msg00192.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> I would find non-stop as a more general solution. In non-stop mode Jan> one still can stop each and all the threads manually. But in Jan> all-stop mode one cannot keep the (other) threads running. [...] Jan> all-stop mode could be also emulated probably from the GDB client side. I thought Pedro talked about this once, but I can't find the message. This seems like a reasonable future project for us -- it seems to me that if ugdb does the thread-specific stop filtering, then it would make sense to notify it of thread-specific breakpoints, and then always use non-stop. Tom