From: Olaf Dabrunz <od@suse.de>
To: Jim Houston <jim.houston@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: kernel trace (with KDB)
Date: Sat, 24 Apr 2004 01:55:21 +0200 [thread overview]
Message-ID: <20040423235521.GA19942@suse.de> (raw)
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?
Regards,
--
Olaf Dabrunz (od/odabrunz), SUSE Linux AG, Nürnberg
next reply other threads:[~2004-04-23 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 23:55 Olaf Dabrunz [this message]
2004-04-24 3:44 ` kernel trace (with KDB) Jim Houston
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=20040423235521.GA19942@suse.de \
--to=od@suse.de \
--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