public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: jim.houston@comcast.net
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	amitkale@emsyssoft.com, linux-kernel@vger.kernel.org
Subject: [PATCH]Call frame debug info for 2.6 kernel
Date: Mon, 22 Mar 2004 16:17:14 -0800	[thread overview]
Message-ID: <405F820A.7010705@mvista.com> (raw)
In-Reply-To: <m33c8788ac.fsf@new.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

This patch adds call frame debug record generation for entry.S frames.  If used 
with KGDB and gdb 6.0 it allows correct "back trace" (bt) through interrupt, 
system call and trap frames.  Frames that point to user space are tied off, 
those that point to the kernel unwind to the kernel.  It also ties off the 
initial frame in head.S and the idle process stacks for cpus other than cpu0 
(which actually goes back to head.S).  The patch adds one (1) instruction to the 
executable kernel (a few lines to the debug space, however).

The patch requires a gdb that handles CFI expressions, although it takes pains 
to work around a bug in gdb 6.0's expression analizer (the work around is also 
compatable with a correctly working expression analizer as can be found in the 
CVS version of gdb).  AFAIK gdb 6.0 is the first gdb to handle CFI expressions 
so you must use it to make this patch useful.

Use of earlier gdb's with this patch will not be affected (either for good or bad).
-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml

[-- Attachment #2: kgdb-dwarf-2.6.4-1.0.patch.gz --]
[-- Type: application/x-gzip, Size: 11356 bytes --]

  parent reply	other threads:[~2004-03-23  0:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 21:37 Fixes for .cfi directives for x86_64 kgdb Jim Houston
2004-03-17 23:53 ` Andi Kleen
2004-03-18 16:51   ` Jim Houston
2004-03-19 13:17     ` Amit S. Kale
2004-03-19 19:23       ` Andi Kleen
2004-03-21 13:12         ` Amit S. Kale
2004-03-23  0:17 ` George Anzinger [this message]
     [not found] <1AR5s-75I-27@gated-at.bofh.it>
     [not found] ` <1CHY0-1Uw-9@gated-at.bofh.it>
2004-03-23  2:04   ` [PATCH]Call frame debug info for 2.6 kernel Andi Kleen
2004-03-23 21:45     ` George Anzinger
2004-03-24  6:25       ` Andi Kleen
2004-03-24 16:20         ` George Anzinger

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=405F820A.7010705@mvista.com \
    --to=george@mvista.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=amitkale@emsyssoft.com \
    --cc=jim.houston@comcast.net \
    --cc=linux-kernel@vger.kernel.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