From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: 32-bit gcore on amd64
Date: Fri, 20 Feb 2004 23:44:00 -0000 [thread overview]
Message-ID: <200402202344.i1KNiDQC027152@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <403676EB.2070803@gnu.org> (message from Andrew Cagney on Fri, 20 Feb 2004 16:06:51 -0500)
Date: Fri, 20 Feb 2004 16:06:51 -0500
From: Andrew Cagney <cagney@gnu.org>
> Well, it can determine the target from ABFD. It certainly can make
> the distinction between a 32-bit and a 64-bit BFD. However, some
> targets, most notably ELF, are shared by various OSes.
So in theory. Wonder if this is something better handled directly by
GDB - who, other than gdb wants to create corefiles?
Why shouldn't objdump be able to write a core file?
;-)
But seriously, yes I think we should let GDB handle the gory details.
BFD should only provide the basic, generic functionality. For ELF
this means we'd keep the generic functionality to write core file
notes (i.e. elfcore_write_note()) in BFD, but move the functions that
create the OS-specific data structure inside those notes
(i.e. elfcore_write_prpsinfo() and elfcore_write_prstatus()) into GDB.
Mark
next prev parent reply other threads:[~2004-02-20 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 23:12 Andrew Cagney
2004-02-19 23:24 ` Daniel Jacobowitz
2004-02-20 0:17 ` Andrew Cagney
2004-02-21 2:25 ` Daniel Jacobowitz
2004-02-20 19:59 ` Mark Kettenis
2004-02-20 21:06 ` Andrew Cagney
2004-02-20 23:44 ` Mark Kettenis [this message]
2004-02-19 23:47 Ulrich Weigand
2004-02-20 18:56 ` Andrew Cagney
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=200402202344.i1KNiDQC027152@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.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