A log message should be generated at a warning level verbosity if the CPU Profiler is included but no CPUPROFILE is specified

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Link an executable against libprofiler.so
2. Execute with a purposely misspelled env 'PERFTOOLS_VERBOSE=99 
*CPU_PROFILE*=/tmp/cpu <executable>'
3. Scratch your head as you wonder why this is all that you see on the console:
<GoogleModuleObject> constructing: atomicops_x86
<GoogleModuleObject> constructing: profile_main
<GoogleModuleObject> destroying: profile_main
<GoogleModuleObject> destroying: atomicops_x86

What is the expected output? What do you see instead?
I would expect to see some indication that cpu profiling is disabled because no 
CPUPROFILE environment setting was found. 

Original issue reported on code.google.com by chapp...@gmail.com on 3 Mar 2012 at 4:43

[GoogleCodeExporter]

------------------------------------------------------------------------
r162 | chappedm@gmail.com | 2012-10-28 14:28:21 -0400 (Sun, 28 Oct 2012) | 1 
line

issue-411: This commit adds additional logging to the cpu profiler to warn when 
the profiler is run and no CPUPROFILE environment setting can be found. It also 
adds a new environment variable PERFTOOLS_UNITTEST to allow certain modules to 
take action when running under the umbrella of a unit test.
------------------------------------------------------------------------

Original comment by chapp...@gmail.com on 28 Oct 2012 at 6:30

• Changed state: Fixed