Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: gdb@sources.redhat.com
Subject: Upgrading from old gdb version
Date: Sun, 04 Mar 2007 21:34:00 -0000	[thread overview]
Message-ID: <45EB3B6A.30504@eagercon.com> (raw)

I'm trying to upgrade a proprietary target from an old
(well ancient) version of gdb (version 5.3) to the current
version.  In some areas, there have been major changes,
for example, in handling frames and analyzing a function
prologue.

Looking at the documentation, there are several places in
the chapter on Target Architecture Definition which either
are empty (e.g., Frame Interpretation) or there are notes
which say that the documentation is obsolete (Raw and
Virtual Register Representations).  The notes refer to the
bug database and AR index.  Unfortunately, I can't really
see anything in either which give me much of a clue.

Can someone suggest a starting point?

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


             reply	other threads:[~2007-03-04 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 21:34 Michael Eager [this message]
2007-03-05  1:46 ` Daniel Jacobowitz
2007-03-05 18:22   ` Jim Blandy
2007-03-05 19:26     ` Michael Eager

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=45EB3B6A.30504@eagercon.com \
    --to=eager@eagercon.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