inspector: use inspector API for "break on start"#12076
Conversation
|
cc @ofrobots |
There was a problem hiding this comment.
The HandleScope isn't necessary, API functions get one implicitly.
There was a problem hiding this comment.
Just CHECK(args.Length() > 1) and CHECK(args[0]->IsFunction())? This is only called by built-in code, right?
There was a problem hiding this comment.
For now, it is not supposed to be a public API. This might change in the future.
There was a problem hiding this comment.
This effectively breaks on the next call into JS land? If this function were to return instead of calling the function, it would break at the next line in lib/module.js?
There was a problem hiding this comment.
It breaks on the next JS instruction. E.g. I just noticed that it is not breaking inside the wrapper - it seems to break on the wrapper call (e.g. one step is required to reach the same point it was breaking before). It does not make any difference for the tests as the line number and variables are the same.
|
Thank you for the review. I addressed the comments, please take another look. |
There was a problem hiding this comment.
Can you check that session_ != nullptr?
There was a problem hiding this comment.
env->context() might be simpler
|
CI has some challenges but they appear unrelated. |
|
Landed as 7954d2a |
|
cc @eugeneo |
|
@italoacasas - sorry, I forgot to add labels. This code does not need to be ported to pre-8x as those versions still rely on debug context. Thanks! |
This change removes a need for using deprecated debug context for
breaking at the start of the main module.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
inspector