On Fri, Sep 25, 2015 at 11:25 PM, Mark Logan <[email protected]> wrote: > On Friday, September 25, 2015 at 4:26:34 AM UTC-7, Ben Noordhuis wrote: >> The machine code that V8 generates uses a custom calling convention >> that's neither cdecl nor stdcall. I'm not aware of any tooling (that >> works on Windows) that knows how to decode the stack trace. > > Is the calling convention just similar enough to cdecl that stack traces on > OS X / Linux work by chance? I've never had a problem with gdb/lldb.
On UNIX platforms, you can build with `make gdbjit=on` to get human-readable stack traces in gdb and lldb (although lldb's JIT support was a little broken last I checked.) Without gdbjit though, if you got a stack trace that goes all the way back to main(), you got lucky. -- -- 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.
