From: Tom Zanussi <trz@attbi.com>
To: Auge Mike <tobe_better@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tracing the kernel...?
Date: Wed, 11 Jun 2003 12:27:38 -0500 [thread overview]
Message-ID: <3EE7668A.FD978414@attbi.com> (raw)
In-Reply-To: Sea2-F643y9Ow5e9HDk00026862@hotmail.com
Auge Mike wrote:
>
> Hi all,
>
> I really want to know how can I trace or debug the kernel and libc? Is there
> any tools and utilities for that?
>
For tracing, try the Linux Trace Toolkit:
http://www.opersys.com/LTT/index.html
prev parent reply other threads:[~2003-06-11 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 14:05 Tracing the kernel...? Auge Mike
2003-06-11 14:22 ` Olaf Dietsche
2003-06-11 17:27 ` Tom Zanussi [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=3EE7668A.FD978414@attbi.com \
--to=trz@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tobe_better@hotmail.com \
/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