public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: lse-tech@lists.sourceforge.net,
	ltp-coverage@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: 2.5.66-gcov
Date: 28 Mar 2003 16:32:27 -0600	[thread overview]
Message-ID: <1048890755.3367.65.camel@plap> (raw)

There is a new version of the gcov-kernel patch on lse at: 
http://sourceforge.net/project/showfiles.php?group_id=8875&release_id=74815

Changes in this release are: 
-resync with 2.5.66 
-detect gcc version for a section that needs to know that 
-profiling of modules is fixed 

The purpose of this patch is to allow utilization of the gcov tool
against a running kernel.  This is different from most other profiling
methods because it can easily tell you things like: which lines of code
are executed, how many times they are executed, and how often different
branches are taken. 

For anyone interested in this type of research, there is also a new
mailing list at: 
http://lists.sourceforge.net/lists/listinfo/ltp-coverage

Thanks, 
Paul Larson


                 reply	other threads:[~2003-03-28 21:15 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=1048890755.3367.65.camel@plap \
    --to=plars@linuxtestproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=ltp-coverage@lists.sourceforge.net \
    /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