[prof] Attribute ticks in embedded builtins correctly
When attributing ticks to a function, we first check if the current pc matches a section within the dynamic library. If we find a match here, then we don't continue looking within dynamically generated range information, e.g. for JS functions and builtins. This logic breaks when embedded builtins come into play. They live within the libv8.so shared library, and are found when looking up statics. But what we really want is to look up the dynamically generated code-range, which contains more precise information. In this CL, this case is detected by matching the found symbol name. If it's the embedded blob, then we continue to dynamic lookup. Bug: v8:6666 Change-Id: I7cea2cd4898f5a08381a071bdbc2f862b9c80880 Reviewed-on: https://chromium-review.googlesource.com/1023422 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#52723}
Showing
Please
register
or
sign in
to comment