public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Shaun Jackman" <shaunj@gray-interfaces.com>
To: "gdb list" <gdb@sources.redhat.com>
Subject: remote debugging
Date: Tue, 15 Aug 2000 10:13:00 -0000	[thread overview]
Message-ID: <004e01c006dc$056bda60$6801a8c0@gray.internal> (raw)

What is the preferred method for remote debugging?

I have an Atmel EB01, AT91M40400 processor (ARM7TDMI) which came with an
Angel monitor in flash.
Debugging with it is dead slow. Stepping through a few lines of code which
occurs as fast as I can click in the simulator takes ~20 seconds with the
Angel monitor. Also, I am unable to connect to the Angel monitor faster than
9600 (although I can go up to 38400 with the Arm Ltd. debugger).

I have a Jeeni on loan (JTAG Angel over ethernet) which allows me to debug
as fast as the simulator, but they're bloody expensive! I'd prefer a serial
or parallel solution if possible, only for cost reasons. (unless someone
knows of a cheap ethernet device!)

Is serial-tether debugging necessarily as slow as the Angel monitor? Would
Cygmon or the gdb-stub be better?

My preferred development environment would be Linux, but I'm stuck in a
dual-booting limbo right now until I can sort out my tool-chain problems.

Many thanks,
Shaun Jackman


             reply	other threads:[~2000-08-15 10:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15 10:13 Shaun Jackman [this message]
2000-08-15 12:23 ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
2015-03-07 13:52 Remote debugging Russell Shaw
2015-03-07 14:09 ` Ofir Cohen
2015-03-08  7:48   ` Russell Shaw
2004-03-22 14:23 luca risso
2004-03-19 17:59 luca risso
2004-03-19 18:43 ` Daniel Jacobowitz
2003-06-13 14:24 remote debugging nak26
2003-06-13  7:50 Brijesh Shukla
2003-06-13 13:28 ` Quality Quorum
2003-03-20  7:45 Patricia Alba
2002-12-12  9:29 Remote Debugging Tim
2002-12-12 10:30 ` Daniel Jacobowitz
2002-07-22  9:35 remote debugging Vinayak P Risbud
2001-01-25  5:27 malar kavi
2001-01-25 11:46 ` J.T. Conklin
2001-01-23 22:23 malar kavi
2001-01-24  6:16 ` Fernando Nasser
2001-01-24 10:52 ` J.T. Conklin
2000-11-30 22:27 Remote Debugging Yu Xuanwei
2000-12-01 11:40 ` Fernando Nasser
2000-11-29 19:52 Yu Xuanwei
2000-11-28  0:59 Remote debugging Yu Xuanwei
2000-04-01  0:00 Remote Debugging Timo Ketola
2000-02-23 19:12 ` Andrew Cagney
2000-04-01  0:00   ` Andrew Cagney

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='004e01c006dc$056bda60$6801a8c0@gray.internal' \
    --to=shaunj@gray-interfaces.com \
    --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).