From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>,
Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: Peter.Barada@motorola.com, gdb@sources.redhat.com
Subject: Re: Torubles with remote stub for m68k
Date: Mon, 24 Jun 2002 15:30:00 -0000 [thread overview]
Message-ID: <3D179D6C.7040904@cygnus.com> (raw)
In-Reply-To: <20020624220628.GB31470@branoic.them.org>
> 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.
cf gdb/274.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=274
Andrew
next prev parent reply other threads:[~2002-06-24 22:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 12:46 [MI/testsuite] mi_gdb_test: expected result priority? Keith Seitz
2002-06-24 13:20 ` Elena Zannoni
2002-06-24 14:04 ` Torubles with remote stub for m68k Peter Barada
2002-06-24 14:13 ` Daniel Jacobowitz
2002-06-24 14:40 ` Peter Barada
2002-06-24 14:56 ` Peter Barada
2002-06-24 15:07 ` Daniel Jacobowitz
2002-06-24 15:30 ` Andrew Cagney [this message]
2002-06-24 15:35 ` Quality Quorum
2002-06-25 7:53 ` Peter Barada
2002-06-25 10:44 ` Andrew Cagney
2002-06-25 9:38 ` Peter Barada
2002-06-25 13:28 ` Andrew Cagney
2002-06-25 10:02 ` Daniel Jacobowitz
2002-06-25 8:13 ` Peter Barada
2002-06-25 8:17 ` Daniel Jacobowitz
2002-06-25 8:32 ` Peter Barada
2002-06-25 8:40 ` Daniel Jacobowitz
2002-06-25 13:43 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D179D6C.7040904@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Peter.Barada@motorola.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=pbarada@mail.wm.sps.mot.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox