mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: piet@bluelane.com
Cc: vgoyal@in.ibm.com, George Anzinger <george@wildturkeyranch.net>,
	Andrew Morton <akpm@osdl.org>,
	Discussion "list for crash utility usage,
	maintenance and development"  <crash-utility@redhat.com>,
	kgdb-bugreport@lists.sourceforge.net,
	Subhachandra Chandra <schandra@bluelane.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel.
Date: Wed, 30 Aug 2006 14:53:00 -0700	[thread overview]
Message-ID: <20060830145300.7d728f6c.rdunlap@xenotime.net> (raw)
In-Reply-To: <1156974093.29300.103.camel@piet2.bluelane.com>

On Wed, 30 Aug 2006 14:41:32 -0700 Piet Delaney wrote:

> On Wed, 2006-08-30 at 16:40 -0400, Vivek Goyal wrote:
> > On Wed, Aug 30, 2006 at 12:35:21PM -0700, Piet Delaney wrote:
> > > > 
> > > > Simple question -- and to be quite honest with you -- I don't
> > > > understand why you wouldn't want to simply use gdb alone
> > > > in this case?
> > > 
> > > I don't see any reason for core file not to be read correctly by
> > > gdb. It's convenient to use gdb directly sometimes, for example
> > > while using the ddd GUI.
> > > 
> > 
> > You can run gdb to open core files as of today but the debugging
> > capability will be limited. For ex. kernel core headers have the info
> > of linearly mapped region only and they don't contain the virt address
> > info of non-linearly mapped regions. So one can not debug the non-linearly
> > mapped regions like modules.
> 
> Amit's modified gdb might help for that problem. I haven't used
> it but it allows gdb to load debug information about modules. You
> can also use a script Amit wrote to explicitly load module info
> into stock gdb; that also might work with kernel core files.
> 
> > 
> > > kgdb isn't having any problems with kernel threads back traces.
> > > The kernel objects are tweaked with dwarf code, but I see no
> > > problem with using the same paradigm with crash. Works great.
> > > 
> > 
> > Can you give some more details on what do you mean by kernel objects
> > are tweaked with dwarf code. 
> 
> Attached is the cfi_annotations.patch patch from the kgdb-2.6.16 patch
> which is part of the kgdb patch series. I believe George Anzinger used 
> a similar dwarf patch in the 2.6 mm series patches that Andrew provided.
> I think Tom Rini wrote both of them. 

ENOPATCH

---
~Randy

  parent reply	other threads:[~2006-08-30 21:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44EC8CA5.789286A@redhat.com>
     [not found] ` <20060824111259.GB22145@in.ibm.com>
     [not found]   ` <44EDA676.37F12263@redhat.com>
     [not found]     ` <1156966522.29300.67.camel@piet2.bluelane.com>
     [not found]       ` <20060830204032.GD30392@in.ibm.com>
2006-08-30 21:41         ` Piet Delaney
2006-08-30 21:48           ` Andrew Morton
2006-08-30 22:57             ` Andrew Morton
2006-08-31  2:42               ` How about an enumerated list of issues with the existing kgdb patches? Piet Delaney
2006-08-31  3:00                 ` Andrew Morton
2006-12-13  8:32                   ` Piet Delaney
2006-08-30 21:53           ` Randy.Dunlap [this message]
2006-08-30 22:22             ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Piet Delaney
2006-08-31 14:07               ` Andi Kleen
2006-08-31 14:20                 ` [Kgdb-bugreport] " Tom Rini
2006-08-31 14:43                   ` Andi Kleen
2006-08-31 20:41                   ` Piet Delaney

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=20060830145300.7d728f6c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=crash-utility@redhat.com \
    --cc=george@wildturkeyranch.net \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piet@bluelane.com \
    --cc=schandra@bluelane.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®