Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: gdb@sourceware.org
Subject: Re: V850E simulator, assembler single-step never returns?!?
Date: Mon, 05 Jun 2006 21:02:00 -0000	[thread overview]
Message-ID: <44849BF0.8000105@redhat.com> (raw)
In-Reply-To: <20060605205045.GA691@nevyn.them.org>

Daniel Jacobowitz wrote:

> Yes, that works too :-)

I say this because insight is really stupid. It really doesn't know much 
  about targets, other than the semantics of "target FOO BAR".

Okay, that's not true. There is one place that I recall where Insight 
knows more about the target than gdb. That is (oddly enough) with the 
V850 and the ICE that NEC has. But fortunately, the simulator is being 
used here.

> (In this particular case, I don't know exactly what the Insight button
> used corresponds to - whether it is e.g. stepi or nexti.  I'd guess
> stepi?)

Yeah, the insight execution buttons (run, step, stepi, next, nexti, 
finish, continue) map one-to-one with gdb commands. We do change run a 
little bit, but it eventually either maps to run or continue, depending 
on the target configuration database built into insight.

Keith


  reply	other threads:[~2006-06-05 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 19:42 Torsten Mohr
2006-06-05 20:42 ` Daniel Jacobowitz
2006-06-05 20:44   ` Keith Seitz
2006-06-05 20:50     ` Daniel Jacobowitz
2006-06-05 21:02       ` Keith Seitz [this message]
2006-06-05 22:36     ` Torsten Mohr
2006-06-05 22:41       ` Daniel Jacobowitz
2006-06-06  9:46         ` Torsten Mohr
2006-06-07 23:24           ` Torsten Mohr
2006-06-08  1:22             ` Daniel Jacobowitz
2006-06-08 12:12               ` Torsten Mohr
2006-06-08 21:37               ` Torsten Mohr
2006-06-05 20:34 Torsten Mohr

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=44849BF0.8000105@redhat.com \
    --to=keiths@redhat.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