From: Andi Kleen <ak@muc.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, george@mvista.com, pavel@ucw.cz,
"Amit S. Kale" <amitkale@emsyssoft.com>
Subject: Re: kgdb for mainline kernel: core-lite [patch 1/3]
Date: Mon, 08 Mar 2004 17:57:26 +0100 [thread overview]
Message-ID: <m3hdwz9szt.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1xuS8-83Q-11@gated-at.bofh.it> (Tom Rini's message of "Mon, 08 Mar 2004 16:30:38 +0100")
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.
-Andi
next parent reply other threads:[~2004-03-08 16:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1xpyM-2Op-21@gated-at.bofh.it>
[not found] ` <1xqXN-44F-13@gated-at.bofh.it>
[not found] ` <1xr7w-4c4-9@gated-at.bofh.it>
[not found] ` <1xrqW-4rh-51@gated-at.bofh.it>
[not found] ` <1xuS8-83Q-11@gated-at.bofh.it>
2004-03-08 16:57 ` Andi Kleen [this message]
2004-03-08 17:18 ` kgdb for mainline kernel: core-lite [patch 1/3] Tom Rini
2004-03-09 4:29 ` Amit S. Kale
2004-03-09 4:36 ` Amit S. Kale
2004-03-10 12:36 ` Andi Kleen
2004-03-10 15:27 ` Tom Rini
2004-03-11 4:57 ` Amit S. Kale
2004-03-11 5:05 ` Randy.Dunlap
2004-03-11 5:11 ` Andi Kleen
2004-03-08 9:39 Amit S. Kale
2004-03-08 9:54 ` Andrew Morton
2004-03-08 10:15 ` Amit S. Kale
2004-03-08 10:26 ` Andrew Morton
2004-03-08 10:49 ` Amit S. Kale
2004-03-08 11:07 ` Andrew Morton
2004-03-08 11:20 ` Amit S. Kale
2004-03-08 11:44 ` Amit S. Kale
2004-03-08 11:54 ` Andrew Morton
2004-03-08 12:00 ` Amit S. Kale
2004-03-08 15:19 ` Tom Rini
2004-03-08 22:26 ` George Anzinger
2004-03-09 8:58 ` Amit S. Kale
2004-03-08 22:19 ` George Anzinger
2004-03-09 5:08 ` Amit S. Kale
2004-03-09 15:37 ` Tom Rini
2004-03-08 11:48 ` Andrew Morton
2004-03-08 22:21 ` George Anzinger
2004-03-08 15:22 ` Tom Rini
2004-03-08 16:32 ` Amit S. Kale
2004-03-08 22:29 ` George Anzinger
2004-03-08 22:15 ` George Anzinger
2004-03-09 4:46 ` Amit S. Kale
2004-03-09 9:29 ` Amit S. Kale
2004-03-09 15:06 ` Tom Rini
2004-03-10 4:05 ` Amit S. Kale
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=m3hdwz9szt.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.org \
/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