I think you just learned to live with the bug and get the best of what's working. Consider how much better that would be if you could not only distinguish user vs. non-user scripts by comparing opaque numbers (which, BTW, can change), but also identify with certainty your scripts by matching script IDs to those you fed into the v8.
Well, it doesn't look like it's going to be fixed any time soon, so I will build a map of compiled resource names and search the script referenced in `v8::Message` by name in this map. This is not as fast as using a vector index, but it will have to do for now. Thanks for your insights, Ben, as always. Andre On Friday, 1 June 2018 11:48:34 UTC-4, Ben Noordhuis wrote: > > On Fri, Jun 1, 2018 at 4:22 PM, A.M. <cis7...@gmail.com <javascript:>> > wrote: > > As for the arbitrary number, it has no usefulness on its own - unless I > can > > link it back to the script that triggered the exception with this > message, > > how would you possibly use almost a random value that has no relation to > the > > script that triggered that exception? > > I use it for matching stack frames (v8::StackFrame::GetScriptId()) to > scripts, to know what frames are worth inspecting (user scripts vs. > non-user scripts.) > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
