-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
--prof-process
CLI args no longer work in 10.10.0
#22786
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Are those arguments documented somewhere? I didn't know about them before you opened this issue |
This looks like an argument being passed down to the v8 scripts by v8_prof_processor.js, it's supposed to be treated as an exec argument but the file is run by us when node/lib/internal/v8_prof_processor.js Lines 31 to 37 in 03b8258
|
Would #22392 could be the culprit too – either way, this is probably my fault. |
Maybe we should just break out of the argument parse loop once we reach |
Make sure that options after `--prof-process` are not treated as Node.js options. Fixes: nodejs#22786
Proposed fix in #22790, would be cool if you could try that? |
We can definitely explore getting clinic into citgm |
Make sure that options after `--prof-process` are not treated as Node.js options. Fixes: #22786 PR-URL: #22790 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Bryan English <bryan@bryanenglish.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Make sure that options after `--prof-process` are not treated as Node.js options. Fixes: #22786 PR-URL: #22790 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Bryan English <bryan@bryanenglish.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Make sure that options after `--prof-process` are not treated as Node.js options. Fixes: #22786 PR-URL: #22790 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Bryan English <bryan@bryanenglish.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Prior Node 10.10.0, the
node --prof-process
tool could be passed arguments altering its behavior. For example,--preprocess
could be passed to deliver JSON data, and-j
to only show JS VM ticks.It seems that in Node 10.10.0, none of the
--prof-process
-specific arguments work anymore.This currenly breaks
0x
,clinic flame
and probably some other perf-analysis tools.e.g.
Node 10.9.0
Node 10.10.0
I think this might be because of #22490. (/cc @addaleax)
The text was updated successfully, but these errors were encountered: