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 <ashley.chek...@gmail.com>
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/v8-dev/CAKSzg3TiGt0-_M%3Dboaxy7D%2Ba9Xt9Tr6WscdsDutm9j38z7bs3Q%40mail.gmail.com.
