From 2b3c76f023b2cd26dd4cee0b45240a2f0f531fc0 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 16 Apr 2013 12:34:44 -0700 Subject: dev-manual: Edits to "Profiling with OProfile" section. (From yocto-docs rev: 4530c0580667e54fdcc84aa4eb2d5e73ab23fca6) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index f39b5b1f39..b62dee12f4 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -4253,7 +4253,7 @@ OProfile is a statistical profiler well suited for finding performance - bottlenecks in both userspace software and in the kernel. + bottlenecks in both user-space software and in the kernel. This profiler provides answers to questions like "Which functions does my application spend the most time in when doing X?" Because the OpenEmbedded build system is well integrated with OProfile, it makes profiling @@ -4293,7 +4293,8 @@ DEBUG_BUILD variable to "1" in the local.conf configuration file. If you use the DEBUG_BUILD variable, - you will also add extra debug information that can make the debug packages large. + you also add extra debugging information that can make the debug + packages large.
-- cgit v1.2.3-54-g00ecf