From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12584 invoked by alias); 25 Jun 2008 15:04:24 -0000 Received: (qmail 12574 invoked by uid 22791); 25 Jun 2008 15:04:22 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 25 Jun 2008 15:04:04 +0000 Received: (qmail 4464 invoked from network); 25 Jun 2008 15:04:02 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 25 Jun 2008 15:04:02 -0000 From: Pedro Alves To: Daniel Jacobowitz Subject: Re: [RFA] set/show enable-software-singlestep Date: Wed, 25 Jun 2008 15:38:00 -0000 User-Agent: KMail/1.9.9 Cc: gdb-patches@sourceware.org, Joel Brobecker , Michael Snyder References: <1214331534.3601.1211.camel@localhost.localdomain> <200806251514.40869.pedro@codesourcery.com> <20080625144215.GA12011@caradoc.them.org> In-Reply-To: <20080625144215.GA12011@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806251603.51908.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00439.txt.bz2 A Wednesday 25 June 2008 15:42:15, Daniel Jacobowitz escreveu: > On Wed, Jun 25, 2008 at 03:14:38PM +0100, Pedro Alves wrote: > > A Wednesday 25 June 2008 14:34:57, Daniel Jacobowitz wrote: > > > I think it should already be auto. can-use-software-singlestep is > > > unintuitive - either do use it, don't use it, or use GDB's best > > > judgement. And if the user selects to use it and it isn't supported, > > > that's an error when we next want to singlestep. WDYT? > > > > Well, not really auto. If a ARM stub does software singlestepping itself > > (say we add it to gdbserver), gdb will still do software > > single-stepping (breakpoint dance), wont it? > > What Joel said elsewhere in the thread just now. If we get a stub > that reports definitively that it can single step, that should take > priority over GDB knowing that software singlestep is implemented for > this architecture. > What I said elsewhere in the thread just now. :-) The stub should report it, and a new target method is required, that takes precedence for stepping operations. > Um, uh-oh. This will break the overloading of software single step > for bypassing atomic operations. Clearly more thought is required! > The stub should just either step it all atomically, and GDB sees only one SIGTRAP, or we force continuing over the sequence with a single-step breakpoint (as we do today), not telling the stub to step at all (as we don't do today...). We seems we need to distinguish this in the reporting mechanism. Another issue is that the atomic operations bypassing is implemented inside the software_singlestepping gdbarch methods. It should be factored out. > Another unfortunate note: we can't trust the vCont reply for this even > though it's clearly the right thing :-( Since current versions of GDB > reject replies without s/S. Yep, I noticed that. We'll need something else, probably qSupported (if we're thinking of supporting multi arch stubs, care must be taken here as well). -- Pedro Alves