From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Vivek Goyal <vgoyal@in.ibm.com>, Andrew Morton <akpm@osdl.org>,
gdb <gdb@sources.redhat.com>, Dave Anderson <anderson@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
fastboot <fastboot@lists.osdl.org>
Subject: Re: [Fastboot] Re: Query: Kdump: Core Image ELF Format
Date: Wed, 9 Mar 2005 20:36:45 +0530 [thread overview]
Message-ID: <20050309150644.GA4663@in.ibm.com> (raw)
In-Reply-To: <m1ll8wlx82.fsf@ebiederm.dsl.xmission.com>
On Wed, Mar 09, 2005 at 07:17:49AM -0700, Eric W. Biederman wrote:
> Vivek Goyal <vgoyal@in.ibm.com> writes:
>
> > On Tue, 2005-03-08 at 11:00 -0700, Eric W. Biederman wrote:
> >
> > This also requires, setting the kernel virtual addresses while preparing
> > the headers. KVA for linearly mapped region is known in advance and can
> > be filled at header creation time and gdb can directly operate upon this
> > region.
>
> I have no problems decorating the ELF header you are generating
> in user space with virtual addresses assuming we can reliably
> get that information. And before a kernel crashes looks like a reasonable
> time to ask that question. I don't currently see where you could
> derive that information.
>
> Beyond that I prefer a little command line tool that will do the
> ELF64 to ELF32 conversion and possibly add in the kva mapping to
> make the core dump usable with gdb. Doing it in a separate tool
> means it is the developer who is doing the analysis who cares
> not the user who is capturing the system core dump.
Well, as a kernel developer, I am both :) For me, having to install
half-a-dozen different command line tools to get and analyze a crash dump
is a PITA, not to mention potential version mismatches. As someone
who would like very much to use crash dump for debugging, I would
much rather be able to force a dump and then use gdb for
a quick debug. I agree that a customer would see a different
situation. It would be nice if we can cater to both the kinds.
Thanks
Dipankar
next prev parent reply other threads:[~2005-03-09 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 12:50 Query: Kdump: Core Image ELF Format vivek goyal
2005-03-08 15:14 ` Dave Anderson
2005-03-08 18:11 ` Eric W. Biederman
2005-03-08 19:26 ` Dave Anderson
2005-03-08 18:00 ` Eric W. Biederman
2005-03-09 6:43 ` Vivek Goyal
2005-03-09 14:17 ` [Fastboot] " Eric W. Biederman
2005-03-09 15:06 ` Dipankar Sarma [this message]
2005-03-10 7:11 ` Eric W. Biederman
2005-03-10 5:02 ` Vivek Goyal
2005-03-10 6:56 ` Eric W. Biederman
2005-03-15 5:49 ` Vivek Goyal
2005-03-10 8:16 ` Itsuro Oda
2005-03-09 6:57 ` Itsuro Oda
2005-03-23 4:26 ` Fernando Luis Vazquez Cao
2005-03-23 10:36 ` Vivek Goyal
2005-03-23 19:54 ` Eric W. Biederman
2005-03-23 19:47 ` [Fastboot] " Eric W. Biederman
[not found] ` <200503300258.34239.mark.williamson@cl.cam.ac.uk>
2005-03-30 7:42 ` Eric W. Biederman
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=20050309150644.GA4663@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=anderson@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=gdb@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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 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.