So I've learned that the issue is caused by a missing SourcePosition from the SourcePositionTable. Does anybody know where the SourcePositionTable is created (where the actual data is specified) for UnoptimizedFrame? This problem shows up during a call to UnoptimizedFrame::Summarize, but it's indicative of an issue occurring earlier on in the compilation process. On Monday, April 8, 2024 at 6:51:51 PM UTC Ashley Chekhov wrote:
> It's good to know that this isn't a necessary evil then. Will keep > looking, thanks =) > > On Monday, April 8, 2024 at 8:34:41 AM UTC Jakob Kummerow wrote: > >> I think we generally expect reported source locations to be correct, >> including from optimized code. I don't know where the bug might be when >> that isn't working. >> >> >> On Mon, Apr 8, 2024 at 10:22 AM Ashley Chekhov <[email protected]> >> wrote: >> >>> I've been trying to track down a bug in reported location of source code >>> that causes errors in node's error reporting (i.e. The wrong part of the >>> code is shown). I have discovered that it is due to optimizations/jit, as >>> the error does not occur when I preface the test code with "eval("");". Do >>> you think this is even salvageable or is it just an inherent limitation of >>> translation to machine code? If not, do you have any advice on where I >>> should look for a solution? >>> >>> -- -- 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/5f1e3102-cb24-41e1-b9de-b23b779e20b8n%40googlegroups.com.
