It's dynamically generated code, so a profiler won't be able to instrument it and you'll get wildly inaccurate results. I'd suggest trying something like valgrind, but I know that fails to run too. There's a profiler in V8 that you could try, I haven't used it myself, so I'm afraid I can't comment. Being on Mac OS, you could also try the DTrace-backed Instruments, assuming V8 sets up a C-like call stack.
On Fri, Mar 12, 2010 at 3:50 AM, <[email protected]> wrote: > Running it with -lprofiler I get a different picture: > > (pprof) top > Total: 2188 samples > 1427 65.2% 65.2% 1427 65.2% _setlocale > 173 7.9% 73.1% 173 7.9% 0x00000001058385f5 > 140 6.4% 79.5% 140 6.4% v8::internal::String::WriteToFlat > 87 4.0% 83.5% 87 4.0% v8::internal::FreeListNode::set_size > 58 2.7% 86.2% 58 2.7% 0x00007fffffe00b85 > 43 2.0% 88.1% 43 2.0% v8::String::WriteAscii > 28 1.3% 89.4% 28 1.3% _telldir$INODE64$UNIX2003 > 25 1.1% 90.5% 25 1.1% _sha1_block_asm_data_order > 21 1.0% 91.5% 21 1.0% v8::internal::Heap::IterateRSet > 18 0.8% 92.3% 81 3.7% v8::internal::MoveElements > 16 0.7% 93.1% 16 0.7% __vproc_grab_subset > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- Thank you Abdulla -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
