From: John Levon <levon@movementarian.org>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>,
crash-utility@redhat.com
Subject: Re: [PATCH][RFC] dump-core: PFN-GMFN table and ELF formatify (was Re: xc_get_pfn_list() creates broken core files)
Date: Wed, 17 Jan 2007 13:06:33 +0000 [thread overview]
Message-ID: <20070117130633.GA28174@totally.trollied.org.uk> (raw)
In-Reply-To: <20070117055451.GB15865%yamahata@valinux.co.jp>
On Wed, Jan 17, 2007 at 02:54:51PM +0900, Isaku Yamahata wrote:
> Do you have any other correct value?
> e.g. ELFOSABI_NONE
NONE seems righter.
> I followed the way creating process core file and linux kernel dump file.
> Process core file and linux kernel dump file use only program headers.
But in both of those cases we have access to meaningful virtual address
maps, which isn't true here (or certainly not trivially true!)
> They use note section pointed by a program header to store register
> infomations and etc.
> Creating sections requires string table to store section name.
> It makes dump-core code more compilated.
> If using sections is appropreate for dump-core, such compilcations
> might be acceptable.
> However I don't see why section is more appropreate than program
> header because I don't expect to have so many kind of notes.
> At least for dump-core.
We want the same format for everything. And e.g. objcopy is designed for
manipulating sections (copying out contents of a section etc). Building
a .shstrstab isn't particularly difficult...
regards
john
next prev parent reply other threads:[~2007-01-17 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 2:45 xc_get_pfn_list() creates broken core files John Levon
2006-11-23 8:52 ` Keir Fraser
2006-11-23 18:16 ` John Levon
2006-11-23 18:39 ` Keir Fraser
2006-11-23 19:17 ` John Levon
2006-11-23 19:20 ` Keir Fraser
2006-11-23 20:52 ` John Levon
2006-11-23 22:05 ` John Levon
2006-11-25 16:03 ` Jimi Xenidis
2006-11-23 23:33 ` Keir Fraser
2006-11-23 23:48 ` John Levon
2007-01-15 9:16 ` [PATCH][RFC] dump-core: PFN-GMFN table and ELF formatify (was Re: [Xen-devel] xc_get_pfn_list() creates broken core files) Isaku Yamahata
2007-01-15 10:13 ` Keir Fraser
2007-01-15 12:38 ` John Levon
2007-01-17 3:59 ` [PATCH][RFC] dump-core: PFN-GMFN table and ELF formatify (was " John Levon
2007-01-17 5:54 ` [PATCH][RFC] dump-core: PFN-GMFN table and ELF formatify (was Re: [Xen-devel] " Isaku Yamahata
2007-01-17 13:06 ` John Levon [this message]
2007-01-18 1:41 ` Isaku Yamahata
2007-01-18 12:42 ` [PATCH][RFC] dump-core: PFN-GMFN table and ELF formatify (was " John Levon
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=20070117130633.GA28174@totally.trollied.org.uk \
--to=levon@movementarian.org \
--cc=crash-utility@redhat.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.