From: vamsi_krishna@in.ibm.com
To: ltc@linux.ibm.com, dprobes@www-124.southbury.usf.ibm.com
Cc: patrick.s.thomson@intel.com, linux-kernel@vger.kernel.org
Subject: [Announce] Dynamic Probes v3.0 Released
Date: Mon, 22 Oct 2001 18:16:32 +0530 [thread overview]
Message-ID: <CA256AED.0045FEC3.00@d73mta01.au.ibm.com> (raw)
Dynamic Probes v 3.0 is released.
Dynamic Probes is a generic and pervasive debugging facility that will
operate under the most extreme software conditions such as debugging a
deep rooted operating system problem in a live environment.
We have released the next major version of Dynamic Probes. It can be
downloaded from the project website at:
http://oss.software.ibm.com/developerworks/opensource/linux/projects/dprobes/
Brief Changelog:
Dynamic Probes can now be built as a kernel module. It now uses generalized
kernel hooks which reduces the overhead on the system when dprobes is
compiled in, but dormant.
- use kernel hooks (gkhi)
- remove system call, dprobes is now a character driver and user-space
interface is through ioctls
- dprobes can be built as a module
- watchpoint probes ("Global Debug Registers"/CONFIG_DR_ALLOC) can now be
turned off in the build
- new call_kmod instruction
- new log target, posix event log
- bug fixes/cleanup in query/getvars
- fix exit to kdb so that backtrace works
- implement ros instruction
- cmdl.l fix to accept '-' in names (mmlnx@linux.ibm.com)
- upgrade to 2.4.12 (patch for 2.4.6 also available)
* please refer to the README in the package for kernel build configuration
options, which have changed significantly. You now need to enable the
Kernel Hooks support to see the DProbes build options.
Regards.. Vamsi.
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5262355 Extn: 3959
Internet: vamsi_krishna@in.ibm.com
reply other threads:[~2001-10-22 12:48 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=CA256AED.0045FEC3.00@d73mta01.au.ibm.com \
--to=vamsi_krishna@in.ibm.com \
--cc=dprobes@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltc@linux.ibm.com \
--cc=patrick.s.thomson@intel.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
all inboxes | Powered by JetHome®