Hi Ben, Thanks for the info!
Is the function-based debug API still supported? Is there any reference or code examples for using that? Jane On Thursday, November 12, 2015 at 4:13:31 AM UTC-8, Ben Noordhuis wrote: > > On Thu, Nov 12, 2015 at 2:22 AM, Jane Chen <[email protected] > <javascript:>> wrote: > > I'd like to be able to do what node.js does in my own embedding > application > > (http://developer.marklogic.com/features/javascript): > > > > ./node --debug -e "console.log('Hello from node.js ' + > process.versions.v8)" > > Debugger listening on port 5858 > > Hello from node.js 4.6.85.28 > > > > I'd like to know v8's roadmap for debugging so that I don't build > something > > that will be deprecated or removed soon. > > V8's HTTP-like debugger protocol has been deprecated and removed. We > emulate it in node.js for backwards compatibility with existing debug > clients. > > The debug agent itself is implemented in terms of > v8::Debug::SetMessageHandler() + v8::Debug::SendCommand() and runs in > a separate thread. > > There's a little bit of additional magic in that sending a SIGUSR1 to > the process will start the debugger with a call to > v8::Debug::DebugBreak(). Caveat emptor: although it works for us, I > don't think V8 makes any guarantees about async signal-safety. That > it works may be an accident of the implementation. > -- -- 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.
