Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Dave Korn'" <dave.korn.cygwin@googlemail.com>, 	<gdb@sourceware.org>
Subject: RE: Software-vs-hardware single-step vs. sim/non-sim targets.
Date: Sat, 05 Dec 2009 21:12:00 -0000	[thread overview]
Message-ID: <013801ca75ef$9ff77a30$dfe66e90$@com> (raw)
In-Reply-To: <4B197BC0.5010708@gmail.com>

>   I have a GDB port for a custom target, a sim-based simulator, and a gdbstub
> for use on the real thing.  GDB can single step the simulator of course, since
> the support for simulated hardware-single-step is built in, but I'd like to
> save bytes in the gdbstub by not implementing support for the "s" command.

Can't you just use gdb-serial as the level of intermediation?

And hide all implementations behind a common facade, and use a single standard
gdb as the front-end?


/jakob


      parent reply	other threads:[~2009-12-05 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 20:58 Dave Korn
2009-12-04 22:08 ` Daniel Jacobowitz
2009-12-05  3:50   ` Dave Korn
2009-12-05  5:58     ` Daniel Jacobowitz
2009-12-05 21:12 ` Jakob Engblom [this message]

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='013801ca75ef$9ff77a30$dfe66e90$@com' \
    --to=jakob@virtutech.com \
    --cc=dave.korn.cygwin@googlemail.com \
    --cc=gdb@sourceware.org \
    /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