I have two ideas. First, the real fix: instead of emitting the current file and line number in the generated CSA, Torque should emit the entire stack of files and line numbers for all macros that are currently entered. That way we wouldn't get a message from just some deeply-nested tiny macro like Is<T> and wonder what other code was including it. I can add this to the Torque backlog if it's not already there.
Second, a possible workaround: assuming that gdb or lldb can at least tell you the name of the builtin and the current offset within it, you could try running mksnapshot with all of the normal args plus --print-code --code-comments, and looking at the disassembly for that builtin near that offset. Perhaps some nearby strings or code comments might give you a hint about the context. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/7893660a-2706-4edc-9892-ee314c17d91eo%40googlegroups.com.
