From: "Amit S. Kale" <amitkale@emsyssoft.com>
Organization: EmSysSoft
To: Tom Rini <trini@kernel.crashing.org>, Andi Kleen <ak@muc.de>
Subject: Re: kgdb for mainline kernel: core-lite [patch 1/3]
Date: Tue, 9 Mar 2004 09:59:15 +0530
User-Agent: KMail/1.5
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org,
       george@mvista.com, pavel@ucw.cz
References: <1xpyM-2Op-21@gated-at.bofh.it> <m3hdwz9szt.fsf@averell.firstfloor.org> <20040308171831.GF15065@smtp.west.cox.net>
In-Reply-To: <20040308171831.GF15065@smtp.west.cox.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200403090959.15556.amitkale@emsyssoft.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1610
Lines: 36

On Monday 08 Mar 2004 10:48 pm, Tom Rini wrote:
> On Mon, Mar 08, 2004 at 05:57:26PM +0100, Andi Kleen wrote:
> > Tom Rini <trini@kernel.crashing.org> writes:
> > > Here's where what Andi said about being able to get the pt_regs stuff
> > > off the stack (I think that's what he said at least) started to confuse
> > > me slightly.  But if I understand it right (and I never got around to
> > > testing this) we can replace the do_schedule() stuffs at least with
> > > something like kgdb_get_pt_regs(), since (and I lost my notes on this,
> > > so it's probably not quite right) (thread_info->esp0)-1
> >
> > No, that's the user space registers.
> >
> > You don't need these registers really as long as you have the
> > correct dwarf2 CFI description of all the code involved. gdb
> > is then able to reconstruct them using the C stack by itself.
> >
> > All it needs for that is esp and eip.
>
> Ah, OK.  Amit, how about for the expanded T-packet thing, we do what you
> suggested, except call it kgdb_arch_extra_regs() and let the arch fill
> out whatever regs it needs to.  ESP/EIP for x86_64/i386, PC/SP for
> ppc32, etc, etc?

That'll be great, though it won't provide any more info to gdb, as gdb can get 
that info by 'g' packet.

Thread listing problem is with 'g' packet returning incomplete information for 
threads other than the current thread.

-Amit

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/