From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23726 invoked by alias); 25 Jun 2002 17:02:01 -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 23700 invoked from network); 25 Jun 2002 17:01:59 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 25 Jun 2002 17:01:59 -0000 Received: from cs2876-108.austin.rr.com ([24.28.76.108] helo=branoic) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17MthR-0001Rp-00; Tue, 25 Jun 2002 12:01:53 -0500 Received: from drow by branoic with local (Exim 3.35 #1 (Debian)) id 17Mtgv-0005C7-00; Tue, 25 Jun 2002 13:01:21 -0400 Date: Tue, 25 Jun 2002 10:02:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Peter Barada , Peter.Barada@motorola.com, gdb@sources.redhat.com Subject: Re: Torubles with remote stub for m68k Message-ID: <20020625170120.GA19950@branoic.them.org> Mail-Followup-To: Andrew Cagney , Peter Barada , Peter.Barada@motorola.com, gdb@sources.redhat.com References: <200206242104.g5OL4pY06652@hyper.wm.sps.mot.com> <20020624211258.GA30001@branoic.them.org> <200206242140.g5OLe0L06792@hyper.wm.sps.mot.com> <200206242156.g5OLumH25691@hyper.wm.sps.mot.com> <20020624220628.GB31470@branoic.them.org> <3D179D6C.7040904@cygnus.com> <200206251452.g5PEq1V26352@hyper.wm.sps.mot.com> <3D189992.4030201@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D189992.4030201@cygnus.com> User-Agent: Mutt/1.3.28i X-SW-Source: 2002-06/txt/msg00254.txt.bz2 On Tue, Jun 25, 2002 at 12:25:54PM -0400, Andrew Cagney wrote: > >Try a: > >> > >>(gdb) maint print architecture OUTPUTFILE > >> > >>and check what the value of the single step macros are. > > > Your specific > >>m68k target (configured as?) may have software single step settings that > >>contradict what the target supports. > > How did you configure your m68k target? > > >Ok, and what do I look for in the dump? I see: > > > >gdbarch_dump: MEMORY_INSERT_BREAKPOINT(addr, contents_cache) # > >(default_memory_insert_breakpoint (addr, contents_cache)) > >gdbarch_dump: MEMORY_REMOVE_BREAKPOINT(addr, contents_cache) # > >(default_memory_remove_breakpoint (addr, contents_cache)) > > > >But what else should I look for? I don't see anything that has 'step' in > >the name. > > SOFTWARE_SINGLE_STEP_P and SOFTWARE_SINGLE_STEP. > > Neither appear to be defined by the m68k targets. This indicates that > the m68k [in current gdb] does not support software single step. Peter was originally talking about memory (software) breakpoints, not software single step; are these important in that case? -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer