Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: gdb-patches@sources.redhat.com
Subject: Re: "No registers" error on connecting to MIPS LSI PMON target
Date: Wed, 08 Oct 2003 14:05:00 -0000	[thread overview]
Message-ID: <20031008140542.GA27876@nevyn.them.org> (raw)
In-Reply-To: <20031008.194759.74756454.nemoto@toshiba-tops.co.jp>

On Wed, Oct 08, 2003 at 07:47:59PM +0900, Atsushi Nemoto wrote:
> I tried to use gdb-6.0 for remote-debugging with MIPS LSI PMON.
> I got a message "No registers." on "target lsi /dev/ttyS0" command.
> 
> I think this is because get_selected_frame() is called BEFORE the
> correct target_ops is installed by push_target().
> 
> This is a temporary patch.  It seems to work, but I can not tell the
> situation mentioned in the "FIXME" comment is really solved or not.
> 
> 
> --- gdb-6.0/gdb/remote-mips.c.org	Wed Jun 11 22:16:28 2003
> +++ gdb-6.0/gdb/remote-mips.c	Wed Oct  8 16:55:19 2003
> @@ -1494,10 +1494,12 @@
>       the request itself succeeds or fails.  */
>  
>    mips_request ('r', 0, 0, &err, mips_receive_wait, NULL);
> +#if 0
>    /* FIXME: cagney/2002-11-29: Force the update of selected frame.
>       This shouldn't be necessary, only many many places still refer to
>       selected_frame directly (instead of using get_selected_frame().  */
>    get_selected_frame (); /* Hack!!!  */
> +#endif
>  }
>  
>  /* Open a connection to the remote board.  */

Hmm, I've got one of these too and see the same error.  This looks to
predate the deprecation of selected_frame, so I think it can probably
go away now.  Andrew would have a better idea...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-10-08 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 10:45 Atsushi Nemoto
2003-10-08 14:05 ` Daniel Jacobowitz [this message]
2003-10-08 19:14   ` Andrew Cagney
2003-10-09 14:37     ` Daniel Jacobowitz
2003-10-12 11:51     ` Atsushi Nemoto

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=20031008140542.GA27876@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=gdb-patches@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