Debugging Chrome Javascript engine source code from Developer Tools

Question

I have some sample JS code that I am running in the browser and it uses Promise. I would like to debug the source code of the JS engine along with debugging my source code. Is there a way I can attach the JS engine source code in chrome developer tools?

UPDATE:

 const buyFlightTicket = () => {
        return new Promise((resolve, reject) => {
            setTimeout(() => {
                const error = false;
                if (error) {
                    reject("Sorry your payment was not successful")
                } else {
                    resolve("Thank you, your payment was successful");
                }
            }, 3000)
        })
    }
    buyFlightTicket()
        .then((success) => console.log(success))
        .catch((error) => console.log(error));

I have this piece of code and I want to understand what the Promise() function is doing with the function I am passing it as argument

The developper tools in chrome include a debugger, is there something you would like to do that's not possible with that? — Mathieu K.
– Mathieu K., Commented Aug 14, 2020 at 10:54
@MathieuK. — They said they wanted to debug V8 itself, not just JS running on it. — Quentin
– Quentin, Commented Aug 14, 2020 at 10:55
I would like to be able to put a breakpoint inside the Engine source code and do some debugging — java_geek
– java_geek, Commented Aug 14, 2020 at 10:56
Yes, the promise constructor passes in two resolving functions as arguments to the executor, which you can (should) call to resolve/reject the promise later. I would suggest you read some promise tutorials to learn the basics, if you want the gory details (or because you learn better that way) I'd suggest you rather read the EcmaScript specification than the source code of an implementation. — Bergi
– Bergi, Commented Aug 14, 2020 at 14:31

jmrk · Accepted Answer · 2020-08-14 11:09:51Z

1

V8 developer here. To debug V8 itself, you need a C++ debugger (like GDB or LLDB or Visual Studio's debugger), along with a Debug build of Chrome or V8. Chrome DevTools can't debug V8's internals.

answered Aug 14, 2020 at 11:09

jmrk

42.1k7 gold badges74 silver badges93 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Debugging Chrome Javascript engine source code from Developer Tools

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related