Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: restore hangs up
Date: Wed, 17 May 2006 11:03:00 -0000	[thread overview]
Message-ID: <20060517004314.GB19174@nevyn.them.org> (raw)
In-Reply-To: <7f45d9390605161732g3fc29755ie7c7ac41bf07e965@mail.gmail.com>

On Tue, May 16, 2006 at 06:32:28PM -0600, Shaun Jackman wrote:
> On arm-elf-gdb 6.4 for target rdi, the restore command hangs up. The
> `Restoring binary' message is the last thing I see. GDB does not
> respond to Ctrl-C. I see that RDI support has been removed from CVS.
> So, three questions:
> 
> 1. Any idea how I can diagnose/work-around this bug in GDB 6.4?

No, since we have no idea what the bug is.

> 2. Can the restore command display some progress information?

You could certainly hack it to; I don't know if it would be generally
useful.

> 3. With a CVS version of gdb (no RDI), is there a recommended way to
> communicate with RDI targets such as the Jeeni JTAG device?

Use a third-party program which converts RDI to the GDB remote
protocol.  There's at least two; one formerly distributed by Cygnus
that you can probably still find (I'm afraid I don't remember the name)
and one in CodeSourcery's ARM releases, which are publicly available.
There might be others, too.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-05-17  0:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17  0:41 Shaun Jackman
     [not found] ` <7f45d9390605161732g3fc29755ie7c7ac41bf07e965@mail.gmail.com>
2006-05-17 11:03   ` Daniel Jacobowitz [this message]
2006-05-17 19:27     ` Shaun Jackman
     [not found]       ` <20060517165538.GA8625@nevyn.them.org>
2006-05-18  0:07         ` Shaun Jackman

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=20060517004314.GB19174@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=sjackman@gmail.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