From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: Is anyone using the HP compilers on PA-RISC with FSF GDB?] (fwd)
Date: Wed, 02 Aug 2006 19:46:00 -0000 [thread overview]
Message-ID: <200608021945.k72JjTmc003026@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20060802192156.GA27488@nevyn.them.org> from "Daniel Jacobowitz" at Aug 2, 2006 03:21:56 pm
> > > There have been requests for ELF debug support. The main issue as
> > > far as I can see is the lack of named sections and where to put stuff.
>
> Do you mean DWARF-2 here? If so, I completely agree. It seems like
Oops, yes DWARF-2.
> SOM has some named sections - at least we're managing to get objdump to
> tell me there's a GDB_STRINGS section - so I don't know what the
> problem is.
Yes, SOM has named spaces and subspaces. However, we backed away from
using named sections in the SOM port a few years ago because there were
issues with them in collect2's processing. Section symbols and name
truncation, when using HP nm, caused problems with constructors/destructors.
There's no problem in generating named subspaces to hold the various
flavors of DWARF-2 debug info. However, there is some dependence
on the presence of named section support in GCC's DWARF-2 output code
as I recall. That's the only issue that needs a little thinking.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2006-08-02 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 19:17 John David Anglin
2006-08-02 19:22 ` Daniel Jacobowitz
2006-08-02 19:46 ` John David Anglin [this message]
2006-08-13 14:59 ` [[RFC] DWARF2 debug support for HP-UX SOM target John David Anglin
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=200608021945.k72JjTmc003026@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=drow@false.org \
--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