From: Jim Houston <jim.houston@comcast.net>
To: Olaf Dabrunz <od@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel trace (with KDB)
Date: 23 Apr 2004 23:44:34 -0400 [thread overview]
Message-ID: <1082778274.993.239.camel@new.localdomain> (raw)
In-Reply-To: <20040423235521.GA19942@suse.de>
On Fri, 2004-04-23 at 19:55, Olaf Dabrunz wrote:
> Hello,
>
> you once submitted a patch implementing a "kernel trace mechanism for
> KDB". Do you have a current version of this patch for 2.6 kernels?
>
> Will function call tracing ever be integrated into KDB?
Hi Olaf,
The last time I had it working was in a linux-2.6.0-test3 based kernel.
If you would like a project, I would be glad to send you what I have.
Jim Houston - Concurrent Computer Corp.
prev parent reply other threads:[~2004-04-24 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 23:55 Olaf Dabrunz
2004-04-24 3:44 ` Jim Houston [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=1082778274.993.239.camel@new.localdomain \
--to=jim.houston@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=od@suse.de \
/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®