public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jie Zhang <jzhang918@gmail.com>
To: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: Questions about software/hardware single step
Date: Tue, 30 Aug 2005 05:21:00 -0000	[thread overview]
Message-ID: <6f48278f050829222013a70b65@mail.gmail.com> (raw)
In-Reply-To: <20050830021418.GB15892@nevyn.them.org>

Daniel,

Thanks. Finally I found a simple way to simulate hardware single step
in simulator.

Jie

On 8/30/05, Daniel Jacobowitz <drow@false.org> wrote:
> On Thu, Aug 18, 2005 at 09:27:09PM +0800, Jie Zhang wrote:
> > I searched the mailing list and found this
> > <http://sourceware.org/ml/gdb/2001-09/msg00179.html>. I took a look at
> > gdbarch.*. It seems that no one has implemented it in the last 4 years.
> > Right?
> 
> Right.  No one's ever had the incentive to work on this or decide the
> best way to resolve it.
> 
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>

      reply	other threads:[~2005-08-30  5:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 13:29 Jie Zhang
2005-08-30  2:14 ` Daniel Jacobowitz
2005-08-30  5:21   ` Jie Zhang [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=6f48278f050829222013a70b65@mail.gmail.com \
    --to=jzhang918@gmail.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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).