public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Schneider, Jan (GE51)" <Jan.Schneider@honeywell.com>
To: 'Steven Johnson' <sjohnson@neurizon.net>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: RE: set architecture for MPC8xx
Date: Thu, 11 Nov 2004 16:49:00 -0000	[thread overview]
Message-ID: <938F1554888BD71194E100B0D0FCD97201AAD7E3@ge51smail2.ge51.honeywell.de> (raw)

ok.
I thought I only need such stub for remote debugging.
Where can I found this stub?
or do I have to implement one?

Jan

-----Original Message-----
From: Steven Johnson [mailto:sjohnson@neurizon.net]
Sent: Wednesday, November 10, 2004 11:12 PM
To: Schneider, Jan (GE51)
Cc: 'gdb@sources.redhat.com'
Subject: Re: set architecture for MPC8xx


Your target stub needs to support the "Architecture" otherwise it wont 
know how to set or get the values of the registers.

If the target stub only reports/handles registers for the "generic" 
architecture, you will need to change it to handle all of the other 
registers.

Steven

Schneider, Jan (GE51) wrote:

>Hello,
>
>I have tried the "set architecture" command for the powerpc MPC8xx. After
>this I see a lot of new registers.
>But for me it seems that these registers aren't really taking effects after
>changing their values.
>I found them in rs6000-tdep.c.
>
>Is there a way to use these additional registers sensible?
>
>thanks
>
>
>  
>

             reply	other threads:[~2004-11-11 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 16:49 Schneider, Jan (GE51) [this message]
2004-11-12  2:21 ` Steven Johnson
  -- strict thread matches above, loose matches on Subject: below --
2004-11-10 20:00 Schneider, Jan (GE51)
2004-11-10 23:53 ` Steven Johnson
2004-11-11 15:07   ` Fabian Cenedese
2004-11-12  2:18     ` Steven Johnson
2004-11-12 15:30       ` 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=938F1554888BD71194E100B0D0FCD97201AAD7E3@ge51smail2.ge51.honeywell.de \
    --to=jan.schneider@honeywell.com \
    --cc=gdb@sources.redhat.com \
    --cc=sjohnson@neurizon.net \
    /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).