Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Shrirang Khishti <shrirangk@kpitcummins.com>
Cc: gdb@sources.redhat.com
Subject: Re: regarding problem in porting gdb
Date: Wed, 21 Dec 2005 11:04:00 -0000	[thread overview]
Message-ID: <8f2776cb0512210304s55c7181am8a6e2d711c943ed2@mail.gmail.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F13094BF11E@sohm.kpit.com>

On 12/21/05, Shrirang Khishti <shrirangk@kpitcummins.com> wrote:
> Hi Jim
>         Thanks for your help and changes suggested by you. But in our
> target GCC we have added a different memory model which handles 32 bits
> of address size  and for that we are not getting any problem. But for
> the memory model  for which  I am  facing the problem we don't need 32
> bits address size(For this model code size is limited to 64K but
> situated at some far address). So in this case it is as good as debug
> info is showing virtual addresses related to program counter

If your PC is only 16 bits long, and the upper bits are provided by
some other register, but the addresses GDB uses to access the target
address space index the larger address space, you may need to define a
gdbarch_read_pc method, and have your 'struct frame_unwind' include a
prev_pc function, to ensure that those upper bits get added as
appropriate.


      parent reply	other threads:[~2005-12-21 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 10:18 Shrirang Khishti
2005-12-21 11:00 ` Jim Blandy
2005-12-21 11:04 ` Jim Blandy [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=8f2776cb0512210304s55c7181am8a6e2d711c943ed2@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb@sources.redhat.com \
    --cc=shrirangk@kpitcummins.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