Calling ProfilerRegisterThread() may not actually register a thread for profiling

[GoogleCodeExporter]

What steps will reproduce the problem?

Have a binary call ProfilerRegisterThread() a couple of times such that
in CpuProfiler::RegisterThread(), the timer_sharing_ variables is set to
TIMERS_SHARED.

Now call fork(). After a fork(), its necessary to setup the timers again
as the settings from setitimer() are not inherited across forks. However,
calling ProfilerRegisterThread() will not work - as the value of 
TIMERS_SHARED in timer_sharing_ will prevent the actual call to 
setitimer. This implies that the fork'd process cannot be profiled.

What version of the product are you using? On what operating system?

Version 1.0. Linux 2.6.27.

Original issue reported on code.google.com by mohit.a...@gmail.com on 5 Feb 2009 at 7:19

• Merged into: #105

[GoogleCodeExporter]

Original comment by `` on 18 Jan 2012 at 9:30

[GoogleCodeExporter]

Original comment by csilv...@gmail.com on 6 Feb 2009 at 3:12

• Changed state: Accepted
• Added labels: Type-Defect

[GoogleCodeExporter]

Original comment by csilv...@gmail.com on 6 Feb 2009 at 3:12

• Added labels: Priority-Medium

[GoogleCodeExporter]

ProfilerRegisterThread is not the right call across a fork -- it really is only 
for
threads.  I believe this is the same issue as issue 105, so I'm merging it with 
that.

Original comment by csilv...@gmail.com on 11 Mar 2009 at 9:04

• Changed state: Duplicate