Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: randolph@tausq.org (Randolph Chung)
Cc: mark.kettenis@xs4all.nl, gdb@sources.redhat.com, brobecker@adacore.com
Subject: Re: Register numbers on hppa64
Date: Sat, 26 Nov 2005 17:34:00 -0000	[thread overview]
Message-ID: <200511261732.jAQHWSYX028560@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <43888F83.7090603@tausq.org> from "Randolph Chung" at Nov 27, 2005 00:38:27 am

> I believe HP compilers for hppa64-hpux also use dwarf; I don't see where 
> the register numbering is documented in the ABI. I can easily implement 
> a hppa64_dwarf_reg_to_regnum method, but I need to know if all hppa64 
> compilers have the same view of register numbers.

I can't provide a definitive answer but I don't think so.  We see
debug information in sections like the following:

  [34] .debug_header     PROGBITS         0000000000000000  00004800
	 0000000000000030  0000000000000000           0     0     4
  [35] .debug_gntt       PROGBITS         0000000000000028  00004830
	 00000000000001a0  0000000000000000           0     0     4
  [36] .debug_lntt       PROGBITS         0000000000001398  000049d0
	 00000000000018f0  0000000000000000           0     0     4

I think this is a modification of the debug format documented in the
32-bit runtime.  At one time, I think there was support for this format
in gdb (wdb?).  However, the practical use is limited as HP libraries
don't contain debug information.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)


  parent reply	other threads:[~2005-11-26 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200511260253.jAQ2rP7Z021130@hiauly1.hia.nrc.ca>
2005-11-26  9:23 ` Randolph Chung
2005-11-26 15:54   ` Mark Kettenis
2005-11-26 16:52     ` Randolph Chung
2005-11-26 17:32       ` Mark Kettenis
2005-11-26 18:50         ` John David Anglin
2005-11-27 16:30         ` Randolph Chung
2005-11-26 17:34       ` John David Anglin [this message]
2005-11-26 17:20     ` John David Anglin
2005-11-26 17:13   ` John David Anglin
2005-11-26 17:52     ` Mark Kettenis
2005-11-26 18:00       ` John David Anglin
2005-11-26 18:31         ` Mark Kettenis
2005-11-27  4:30           ` John David Anglin
2005-11-27 15:10             ` Randolph Chung
2005-11-27 16:52               ` John David Anglin
2005-11-27 17:42               ` Mark Kettenis

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=200511261732.jAQHWSYX028560@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=randolph@tausq.org \
    /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