From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15092 invoked by alias); 15 Jan 2002 16:21:26 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15060 invoked from network); 15 Jan 2002 16:21:25 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 15 Jan 2002 16:21:25 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 6275D3D2E; Tue, 15 Jan 2002 11:21:25 -0500 (EST) Message-ID: <3C445705.6070607@cygnus.com> Date: Tue, 15 Jan 2002 08:21:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Quality Quorum Cc: gdb@sources.redhat.com Subject: Re: software single step - feature request References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00157.txt.bz2 > Hi, > > > There are a few nits associated with soft single step support, which are > easy to work around but annoying enough to justify a fix. Your not alone. This is taken from gdbarch.sh: # FIXME/cagney/2001-01-18: This should be split in two. A target method that indicat es if # the target needs software single step. An ISA method to implement it. # # FIXME/cagney/2001-01-18: This should be replaced with something that inserts breakp oints # using the breakpoint system instead of blatting memory directly (as with rs6000). # # FIXME/cagney/2001-01-18: The logic is backwards. It should be asking if the target can # single step. If not, then implement single step using breakpoints. F:2:SOFTWARE_SINGLE_STEP:void:software_single_step:enum target_signal sig, int insert _breakpoints_p:sig, insert_breakpoints_p::0:0 > 1. Soft single step is configured per platform (e.g. arm-wince has one > and generic arm does not), IMHO, it should be provided on per CPU > basis. > > 2. It has to be provided for every CPU - may be as part of multi-arch > transition. > > 3. It should be run-time configurable - so it should be possible to > use the same gdb image both with and without soft single step. > > 4. If target supports hw single step it should be possible to configure > removal of breakpoints before stepping. > > > Thanks, > > Aleksey see gdb/120