This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Torubles with remote stub for m68k
- From: Quality Quorum <qqi at theworld dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: Daniel Jacobowitz <drow at mvista dot com>, Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>, <Peter dot Barada at motorola dot com>, <gdb at sources dot redhat dot com>
- Date: Mon, 24 Jun 2002 18:35:49 -0400
- Subject: Re: Torubles with remote stub for m68k
On Mon, 24 Jun 2002, Andrew Cagney wrote:
> > With gdb-5, if the stub doesn't use breakpoint registers, is it gdb's
> >> responsibility to save/restore the brekpoint across a 's' packet, or
> >> is that the stub's responsibility?
> >>
> >> Any help is appreciated!
> >
> >
> > If GDB sets the breakpoint using 'M' (or presumably 'X') commands, then
> > it is the client's responsibility to clear it. It would be nice to
> > know why that isn't happening. To observe it in action you can use
> > gdbserver on a GNU/Linux system...
>
> 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.
BTW, it will be nice to have this feature dynamically configurable.
>
> cf gdb/274.
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=274
>
> Andrew
>
>
Thanks,
Aleksey