Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: randolph@tausq.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [hppa-hpux] Core file support for hppa64-hp-hpux11.11
Date: Fri, 18 Nov 2005 04:44:00 -0000	[thread overview]
Message-ID: <200511180008.jAI08jpp000219@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <437D15C4.9000207@tausq.org> (message from Randolph Chung on Fri, 18 Nov 2005 07:44:04 +0800)

> Date: Fri, 18 Nov 2005 07:44:04 +0800
> From: Randolph Chung <randolph@tausq.org>
> 
> > Ok, so your problem is that the core file is marked as "UNIX - System
> > V", so there's no way to tell that this is a HP-UX core file.
> 
> Yes.
> 
> > What I'd do, is create BFD sections out of those HP_CORE_XXX program
> > headers, and then in GDB, check for one of those sections.  There's
> > one program header that looks particularly promising: HP_CORE_KERNEL.
> > That one contains the string HP-UX.  That'd certainly convince me that
> > this is a HP-UX core file.
> 
> [...]
> 
> > Actually I think it makes sense to modify your BFD patch such that it
> > gives all HP_CORE_XXX program headers a sensible name:
> 
> Sure, I'll do that.
> 
> So basically you want:
> 1) BFD to name the HP_CORE_KERNEL phdr as a "core.kernel" section
> 2) GDB in its OSABI sniffer will look for this section and check that 
> its contents contains "HP-UX"
> 
> right?

Yes.  The section will come out as .core.kernel in objdump.  Perhaps
it should be .hp.core.kernel.  I'll leave the naming decision to you
and/or the binutils maintainers.  But I think that's better than
having all those .proc0, .proc1, .proc2 sections that we have now.
And it makes it easier to pick the right one from GDB.

Mark


  reply	other threads:[~2005-11-18  0:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 12:56 Randolph Chung
2005-11-17 14:46 ` Mark Kettenis
2005-11-17 15:52   ` Randolph Chung
2005-11-17 16:02     ` Mark Kettenis
2005-11-18  3:37       ` Randolph Chung
2005-11-18  4:44         ` Mark Kettenis [this message]
2005-11-18 13:49           ` Randolph Chung
2005-11-18 15:30             ` 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=200511180008.jAI08jpp000219@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --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