999e3fca90
The problem appeared due to a fact that stubs doesn't create a stack frame, reusing the stack frame of the caller function. When building stack traces, the current function is retrieved from PC, and its callees are retrieved by traversing the stack backwards. Thus, for stubs, the stub itself was discovered via PC, and then stub's caller's caller was retrieved from stack. To fix this problem, a pointer to JSFunction object is now captured from the topmost stack frame, and is saved into stack trace log record. Then a simple heuristics is applied whether a referred function should be added to decoded stack, or not, to avoid reporting the same function twice (from PC and from the pointer.) BUG=553 TEST=added to mjsunit/tools/tickprocessor Review URL: http://codereview.chromium.org/546089 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
14 lines
582 B
Plaintext
14 lines
582 B
Plaintext
shared-library,"shell",0x08048000,0x081ee000
|
|
shared-library,"/lib32/libm-2.7.so",0xf7db6000,0xf7dd9000
|
|
shared-library,"ffffe000-fffff000",0xffffe000,0xfffff000
|
|
profiler,"begin",1
|
|
code-creation,Stub,0x424260,348,"CompareStub_GE"
|
|
code-creation,LazyCompile,0x2a8100,18535,"DrawQube 3d-cube.js:188"
|
|
function-creation,0x2d11b8,0x2a8100
|
|
code-creation,LazyCompile,0x480100,3908,"DrawLine 3d-cube.js:17"
|
|
function-creation,0x2d0f7c,0x480100
|
|
tick,0x424284,0xbfffeea0,0x2d0f7c,0,0x2aaaa5
|
|
tick,0x42429f,0xbfffed88,0x2d0f7c,0,0x2aacb4
|
|
tick,0x48063d,0xbfffec7c,0x2d0f7c,0,0x2aaec6
|
|
profiler,"end"
|