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

> 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.

actually there's no . prefix unless i explicitly pass one, and they will 
look like:

/home/tausq/core:     file format elf64-hppa

Sections:
Idx Name          Size      VMA               LMA               File off 
  Algn
   0 hp.core.version0 00000004  0000000000000000  0000000000000000 
00000350  2**0
                   CONTENTS, READONLY
   1 hp.core.kernel1 0000003c  0000000000000000  0000000000000000 
00000354  2**0
                  CONTENTS, READONLY
   2 hp.core.comm2 00000009  0000000000000000  0000000000000000 
00000390  2**0
                   CONTENTS, READONLY
   [...]

Does this match what you have in mind?

randolph


  reply	other threads:[~2005-11-18 12:59 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
2005-11-18 13:49           ` Randolph Chung [this message]
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=437DD009.1080302@tausq.org \
    --to=randolph@tausq.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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