mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Piet Delaney <piet@bluelane.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Piet Delaney <piet@bluelane.com>, Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@osdl.org>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	George Anzinger <george@wildturkeyranch.net>,
	vgoyal@in.ibm.com, Subhachandra Chandra <schandra@bluelane.com>,
	Discussion "list for crash utility usage,
	maintenance and development"  <crash-utility@redhat.com>
Subject: Re: [Kgdb-bugreport] [RFC] [Crash-utility] Patch to use gdb's bt in crash - works	great with kgdb! - KGDB in Linus Kernel.
Date: Thu, 31 Aug 2006 13:41:13 -0700	[thread overview]
Message-ID: <1157056874.24314.67.camel@piet2.bluelane.com> (raw)
In-Reply-To: <20060831142036.GF23227@smtp.west.cox.net>

On Thu, 2006-08-31 at 07:20 -0700, Tom Rini wrote:
> On Thu, Aug 31, 2006 at 04:07:15PM +0200, Andi Kleen wrote:
> > Piet Delaney <piet@bluelane.com> writes:
> > > > 
> > > > ENOPATCH
> > > 
> > > Opps. 
> > 
> > What an ugly patch!
> > 
> > But it should be totally obsolete with the unwinder work Jan and me have been
> > doing recently which does this all properly. .18 isn't quite there
> > yet in all cases, but .19 will be hopefully.
> 
> Indeed.  But quite functional.  Have you guys been doing i386 as well?
> This kind of thing was needed to convince gdb when it really was time to
> stop trying unwind in a few cases, but looks quite bad on x86_64/i386.
> Thankfully getting it to stop on ARM was pretty easy (but it wasn't
> full/true annotations).

I wonder if we are killing a fly with a sledgehammer. On SunOS 4.1.4 I
just patched the top of stack with a NULL pointer. With SPARC the kernel
uses different registers than the user and don't recall their being a
problem with a NULL pointer being at the top of the kernel stack. Is
there a problem with the i386 architecture with the top of the kernel
stack having a NULL pointer? My guess is that it's needed to return
to the right place in user space.

-piet

> 
-- 
Piet Delaney
BlueLane Teck
W: (408) 200-5256; piet@bluelane.com
H: (408) 243-8872; piet@piet.net



      parent reply	other threads:[~2006-08-31 20:41 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           ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Randy.Dunlap
2006-08-30 22:22             ` 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 [this message]

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=1157056874.24314.67.camel@piet2.bluelane.com \
    --to=piet@bluelane.com \
    --cc=ak@suse.de \
    --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=schandra@bluelane.com \
    --cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome