On Tue, May 20, 2014 at 3:33 AM, Ben Noordhuis <[email protected]> wrote:
> On Mon, May 19, 2014 at 2:51 PM, Thomas Fankhauser <[email protected]> > wrote: > > Ah, interesting. I'm using the v0.11.14-pre. The dtrace with your > selection > > gave me the following output: > > > >>> dtrace: pid 8657 has exited > >>> > >>> > >>> > >>> libsystem_kernel.dylib`__getpid > >>> > >>> node`node::SetupProcessObject(node::Environment*, int, > char > >>> const* const*, int, char const* const*)+0x4e0 > >>> > >>> 0x101103d60 > >>> > >>> 1 > > > > But at the start it reports some errors: > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x697a696d6974704f) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x70656577533a3876) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x70656577533a3876) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x70656577533a3876) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x70656577533a3876) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x69666f72503a3876) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x742f73726573552f) in action #2 > >> > >> dtrace: error on enabled probe ID 1 (ID 106821: > >> pid8793:libsystem_kernel.dylib:__getpid:entry): invalid address > >> (0x5472656c706d6153) in action #2 > > > > > > I both tried with and without the --prof option with the same result of > only > > 1 probe. > > > > Does that bring you somehow closer? > > I'm afraid not. Maybe file an issue in the node.js bug tracker? > > The dtrace errors you're seeing are fairly benign. ustack on OS X > (and possibly in general) is somewhat buggy; it gets confused when > code moves around, something V8 does. Sadly, the ustack helper (and in some cases, the ustack() action more generally) often doesn't work on OS X. The last update I've seen from Apple is this one: http://www.mail-archive.com/[email protected]/msg04668.html but I'm not sure what's the status on Mavericks. (The problem doesn't have to do with code moving around -- the ustack helper design deliberately accommodates that case -- and I'm not aware of similar problems on other systems, but that probably doesn't help the OP.) -- Dave -- -- 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.
