Jeffrin Jose T
unread,Jul 5, 2019, 3:03:02 PM7/5/19Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to obe...@linux.ibm.com, cor...@lwn.net, linu...@vger.kernel.org, linux-...@vger.kernel.org, clang-bu...@googlegroups.com, Jeffrin Jose T
Fixed an outdated directory path inside gcov related documentation
which is part of an example that shows the way in which the gcov
command should be used in that context
Signed-off-by: Jeffrin Jose T <
jef...@rajagiritech.edu.in>
---
Documentation/dev-tools/gcov.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dev-tools/gcov.rst b/Documentation/dev-tools/gcov.rst
index 46aae52a41d0..e3d262d8c7de 100644
--- a/Documentation/dev-tools/gcov.rst
+++ b/Documentation/dev-tools/gcov.rst
@@ -8,7 +8,7 @@ To get coverage data for a specific file, change to the kernel build
directory and use gcov with the ``-o`` option as follows (requires root)::
# cd /tmp/linux-out
- # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel spinlock.c
+ # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel/locking spinlock.c
This will create source code files annotated with execution counts
in the current directory. In addition, graphical gcov front-ends such
--
2.20.1