Correctly report callstack when current function is FunctionCall builtin

Correctly report callstack when current function is FunctionCall builtin

When current function is FunctionCall builtin we have no reliable way to determine its caller function (in many cases the top of the sampled stack contains address of the caller but sometimes it does not). Instead of dropping the sample or its two top frames we simply mark the caller frame as '(unresolved function)'. It seems like a better approach that dropping whole sample as knowing the top function and the rest of the stack the user should be able to figure out what the caller was.

This change adds builtin id to CodeEntry objects. It will be used later to add similar top frame analysis for FunctionApply and probably other builtins.

BUG=None
TBR=loislo@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=15436

[yurys, 2013-07-02 07:48:08]

This is exactly same change as r15426 that was reverted due to UNREACHABLE
assertion failure. I removed that assert as some of the Code objects may be
filtered out by CpuProfiler and it is fine if they are not in the CodeMap.

[loislo, 2013-07-02 07:48:55]

lgtm

[yurys, 2013-07-02 07:51:19]

Committed patchset #2 manually as r15436 (presubmit successful).