| /external/chromium_org/tools/cygprofile/ |
| cygprofile.gyp | 8 'target_name': 'cygprofile',
12 'cygprofile.cc',
13 'cygprofile.h',
32 'cygprofile',
|
| cygprofile.h | 39 // To make cygprofile truly work (i.e. without any deadlock) on Chrome
40 // platforms that use fork(), cygprofile.cc should be written in a way that
43 // means that cygprofile.cc should not perform any heap allocation (since heap
45 // - Only cygprofile.cc uses pthread_atfork() in the whole process. Unlike POSIX
47 // Calling pthread_atfork() in cygprofile.cc would override any handler that
52 // it's not instrumented with cygprofile, directly calls exec(). This is safe
55 // actually observed by trying to port the current version of cygprofile.cc to
61 namespace cygprofile { namespace
164 } // namespace cygprofile
|
| PRESUBMIT.py | 5 """Top-level presubmit script for cygprofile.
|
| cygprofile_unittest.cc | 5 #include "tools/cygprofile/cygprofile.h"
17 namespace cygprofile { namespace
95 } // namespace cygprofile
|
| cygprofile.cc | 5 #include "tools/cygprofile/cygprofile.h"
31 namespace cygprofile { namespace
161 // (cygprofile.gyp provides that), the called routines are and thus will
373 } // namespace cygprofile
|
| mergetraces.py | 142 which can be greatly impacted when profiling is done with cygprofile. As a
|
| /external/chromium_org/tools/android/md5sum/ |
| BUILD.gn | 29 #'dependencies': [ '../../../tools/cygprofile/cygprofile.gyp:cygprofile', ],
|
| md5sum.gyp | 38 'dependencies': [ '../../../tools/cygprofile/cygprofile.gyp:cygprofile', ],
|
| /external/chromium_org/chrome/ |
| chrome_shell.gypi | 34 'dependencies': [ '../tools/cygprofile/cygprofile.gyp:cygprofile', ],
|
| chrome_exe.gypi | 90 '../tools/cygprofile/cygprofile.gyp:cygprofile',
|
| /external/chromium_org/build/ |
| common.gypi | 449 # See src/third_party/cygprofile/cyg-profile.cc for details.
[all...] |
