On Mon, Jan 4, 2016 at 7:19 PM, Matt Esch <[email protected]> wrote: > Yeah I too need to be compatible with old versions of v8 because I've still > got code on 0.10, I think you're right about writing a new profiler. The > trouble is that most profilers ignore the benefits of being able to see the > syscalls and the full C++ stack we're calling into. I actually think it's > pretty poor for the cpu profiler to bail during GC, since this is a > significant source of cpu churn that is important to know if you're > optimizing a service. Out of curiosity, what are you using to take the > backtrace? The stack can be naively walked, but there are a bunch of > platform-specific nuances and maybe some issues if you use certain GCC > optimizations. I was considering using libunwind though v8 already has some > cross platform stack walking code in it.
We use a fairly simple frame pointer follower for portability reasons. It may miss out optimized frames every now and then but so far that hasn't been an issue. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
