From: Vladimir Prus <ghost@cs.msu.su>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB commands
Date: Mon, 26 Nov 2007 19:21:00 -0000 [thread overview]
Message-ID: <200711262221.26312.ghost@cs.msu.su> (raw)
In-Reply-To: <1196103154.2501.32.camel@localhost.localdomain>
On Monday 26 November 2007 21:52:34 Michael Snyder wrote:
> On Fri, 2007-11-23 at 14:05 +0300, Vladimir Prus wrote:
> > Guillaume MENANT wrote:
> >
> > >
> > > Can't we know which command is mandatory ? I'm assuming that m, M, c, s,
> > > g, and G are mandatory but i'm not sure.
> >
> > I doubt a complete list is available. Off the top of my head, you need
> > vCont (and don't need c and s).
>
> I don't see how that is true -- you can still control a target
> using c and s rather than using vCont...
If the target is multi-threaded, vCont is much better idea. And given
that implementing vCont is about as much work as c/s/Hc, it's probably
better to just implement vCont even for single-threaded target.
> > You also need zN/ZN -- without breakpoints,
> > debugging is of no interest.
>
> Neither is this true -- breakpoints can be set the old fashioned
> way using memory read/write and trap instructions.
Yes, you're right.
- Volodya
next prev parent reply other threads:[~2007-11-26 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 13:44 Guillaume MENANT
2007-11-23 9:37 ` Guillaume MENANT
2007-11-23 11:05 ` Vladimir Prus
2007-11-23 12:27 ` Guillaume MENANT
2007-11-23 12:58 ` Vladimir Prus
2007-11-26 19:04 ` Michael Snyder
2007-11-26 19:21 ` Vladimir Prus [this message]
2007-11-26 19:14 ` Michael Snyder
2007-11-26 19:22 ` Daniel Jacobowitz
2007-11-26 19:30 ` Michael Snyder
2007-11-27 10:46 ` Guillaume MENANT
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=200711262221.26312.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.com \
--cc=msnyder@specifix.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).