-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
src: fix possible dereference of NULL pointer #58459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #58459 +/- ##
==========================================
- Coverage 90.21% 90.19% -0.02%
==========================================
Files 635 635
Lines 187304 187344 +40
Branches 36782 36788 +6
==========================================
+ Hits 168970 168984 +14
- Misses 11093 11140 +47
+ Partials 7241 7220 -21
🚀 New features to boost your workflow:
|
Would you mind updating the commit message following https://github.com/nodejs/node/blob/main/doc/contributing/pull-requests.md#commit-message-guidelines? Thank you! |
There is a CHECK_NOT_NULL check before dereferencing node_env on line 710 in the "if" block, but there is no CHECK_NOT_NULL check before dereferencing node_env on line 721. Maybe it makes sense to put CHECK_NOT_NULL right after calling the Environment::GetCurrent function.
6025590
to
8c14942
Compare
Is everything right now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There is a CHECK_NOT_NULL check before dereferencing node_env on line 710 in the if block, but there is no CHECK_NOT_NULL check before dereferencing node_env on line 721. Maybe it makes sense to put CHECK_NOT_NULL right after calling the Environment::GetCurrent function?