public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: "Ahmed A. Agbabiaka" <ahmed@thyron.com>,
	GDB Mailing List <gdb@sources.redhat.com>,
	insight@sources.redhat.com
Subject: Re: Unable to step through ARM code using insgiht-5.0
Date: Thu, 15 Feb 2001 13:26:00 -0000	[thread overview]
Message-ID: <20010215153104.A16389@visi.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010215112126.14472G-100000@ryobi.cygnus.com>

On Thu, Feb 15, 2001 at 11:30:10AM -0800, Keith Seitz wrote:

> [insight-related]
> > (Note: The "Continue to here" command" ignores ALL break points).
> 
> As discussed in the online help (select "Help->Help Topics..",
> then Source Window and Source Window Pop-up Menus), this is the
> intended behavior.
> 
> I'll leave to others more familiar with ARM support in gdb to
> address your other concerns. I will add, though, that I have
> never had any luck using ARM's rdi implementation (which they
> gave to gdb, no longer maintain, and are no longer interested
> in seeing kept up to date) at anything but 9600 baud.

I use RDI at 19200 (EmbeddedICE) and 38400 (Jeeni) with no
problems under Linux.  The serial/parallel combination also
works well under Linux, though Ethernet (Jeeni) is really the
way to go.

> What host/target are you using? I assume it's probably
> windows-hosted using rdi?

I've heard that serial RDI support under Widows/Cygwin has been
flakey in the past (and not worked at all under some versions
of Cygwin).

-- 
Grant Edwards
grante@visi.com

      parent reply	other threads:[~2001-02-15 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000601c09778$460cfd60$97010110@thyronlocal>
2001-02-15 11:34 ` Keith Seitz
2001-02-15 13:01   ` Fernando Nasser
2001-02-15 14:07     ` Grant Edwards
2001-02-15 13:26   ` Grant Edwards [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=20010215153104.A16389@visi.com \
    --to=grante@visi.com \
    --cc=ahmed@thyron.com \
    --cc=gdb@sources.redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=keiths@cygnus.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).