From: Daniel Jacobowitz <drow@mvista.com>
To: 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: Tue, 25 Jun 2002 08:17:00 -0000 [thread overview]
Message-ID: <20020625151636.GA16694@branoic.them.org> (raw)
In-Reply-To: <200206251512.g5PFCxZ26374@hyper.wm.sps.mot.com>
On Tue, Jun 25, 2002 at 11:12:59AM -0400, Peter Barada wrote:
>
> >> 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...
>
> Huh? That doesn't make sense(at least to me)...
> Why would gdb go to all the trouble of writing the breakpoint and the
> force the stub to remove it? Does the stub have to remove the
> breakpoint when gdb is reading memory(say for x/10i $pc)? How can the
> stub manage an unbounded number of breakpoints this way(wouldn't the
> stub be required to allocate memory)? Where in the documentation is
> this 'symbiosis' mentioned where gdb sets breakpoints and the stub is
> responsible for removing them while stepping?
>
> Besides, this stub works fine with gdb-4.16 and gdb-4.18, so what's changed?
>
> I can see that if the 'Z' commands are used to set breakpoints then
> the stub is responsible for managing them, but not the 'M' command...
>
> Again, any help is appreciated!
Terminology skew. "the client" is GDB, not the stub; the stub is
essentially a server, like gdbserver is.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-25 15:17 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
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 [this message]
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=20020625151636.GA16694@branoic.them.org \
--to=drow@mvista.com \
--cc=Peter.Barada@motorola.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).