From: "Amit S. Kale" <akale@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: kgdb enhancements
Date: Sun, 22 Jul 2001 08:13:03 -0700 [thread overview]
Message-ID: <E15OKul-0001tB-00@usw-pr-shell2.sourceforge.net> (raw)
Hi,
I have restructured the kgdb webpage for better readability and added extensive
documentation. The documentation is still being being written.
kgdb for linux kernel 2.4.6 is available from the downloads page. It has
following improvements over kgdb for 2.4.3 and 2.4.5 kernels.
- Enhanced kgdb with kgdb and kernel asserts.
- Added configuration option for thread analysis. The configuration option
enables code required for thread analysis which is disabled by default to of
the overhead it causes.
- Modified semaphore handling functions so that knowing where a thread is
waiting on a semaphore is easier.
Please visit http://kgdb.sourceforge.net/ to get new kgdb.
Thanks.
--
Amit S. Kale
<akale@users.sourceforge.net>
Linux kernel source level debugger http://kgdb.sourceforge.net/
Translation filesystem http://trfs.sourceforge.net/
reply other threads:[~2001-07-22 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E15OKul-0001tB-00@usw-pr-shell2.sourceforge.net \
--to=akale@users.sourceforge.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