-
Notifications
You must be signed in to change notification settings - Fork 30k
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
wasi: address coverity warning #49866
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
mhdawson
commented
Sep 25, 2023
- add check for case when trying to provide a better Exception fails
- the code was modified to avoid a CHECK_EQ in all cases in wasi: throw on failed uvwasi_init() #31076, however, I believe that if we fail to create the exeption to throw instead of simply returning using a CHECK makes more sense. I think it should also address the coverity warning about not initializing in the constructor.
- add check for case when trying to provide a better Exception fails - the code was modified to avoid a CHECK_EQ in all cases in nodejs#31076, however, I believe that if we fail to create the exeption to throw instead of simply returning using a CHECK makes more sense. I think it should also address the coverity warning about not initializing in the constructor. Signed-off-by: Michael Dawson <[email protected]>
Review requested:
|
nodejs-github-bot
added
c++
Issues and PRs that require attention from people who are familiar with C++.
needs-ci
PRs that need a full CI run.
wasi
Issues and PRs related to the WebAssembly System Interface.
labels
Sep 25, 2023
Coverity warning: 84 if (err != UVWASI_ESUCCESS) {
85 Local<Value> exception;
2. Condition !v8::MaybeLocal<v8::Value>(node::wasi::WASIException(env->context(), err, "uvwasi_init")).ToLocal(&exception), taking true branch.
86 if (!WASIException(env->context(), err, "uvwasi_init").ToLocal(&exception))
4. uninit_member: Non-static class member uvw_.fds is not initialized in this constructor nor in any functions that it calls.
6. uninit_member: Non-static class member uvw_.argc is not initialized in this constructor nor in any functions that it calls.
8. uninit_member: Non-static class member uvw_.argv is not initialized in this constructor nor in any functions that it calls.
10. uninit_member: Non-static class member uvw_.argv_buf is not initialized in this constructor nor in any functions that it calls.
12. uninit_member: Non-static class member uvw_.argv_buf_size is not initialized in this constructor nor in any functions that it calls.
14. uninit_member: Non-static class member uvw_.envc is not initialized in this constructor nor in any functions that it calls.
16. uninit_member: Non-static class member uvw_.env is not initialized in this constructor nor in any functions that it calls.
18. uninit_member: Non-static class member uvw_.env_buf is not initialized in this constructor nor in any functions that it calls.
20. uninit_member: Non-static class member uvw_.env_buf_size is not initialized in this constructor nor in any functions that it calls.
CID 276376 (#2 of 2): Uninitialized pointer field (UNINIT_CTOR)
22. uninit_member: Non-static class member uvw_.allocator is not initialized in this constructor nor in any functions that it calls.
87 return;
88
89 env->isolate()->ThrowException(exception); |
mhdawson
added
request-ci-failed
An error occurred while starting CI via request-ci label, and manual interventon is needed.
request-ci
Add this label to start a Jenkins CI on a PR.
and removed
request-ci-failed
An error occurred while starting CI via request-ci label, and manual interventon is needed.
labels
Sep 28, 2023
github-actions
bot
removed
the
request-ci
Add this label to start a Jenkins CI on a PR.
label
Sep 28, 2023
cjihrig
approved these changes
Sep 28, 2023
is this condition reachable when the isolate is terminated? |
This was referenced Sep 30, 2023
Since there is a return code from the function around which the CHECK as been added I believe it should be reachable. |
mhdawson
added a commit
that referenced
this pull request
Oct 12, 2023
- add check for case when trying to provide a better Exception fails - the code was modified to avoid a CHECK_EQ in all cases in #31076, however, I believe that if we fail to create the exeption to throw instead of simply returning using a CHECK makes more sense. I think it should also address the coverity warning about not initializing in the constructor. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #49866 Reviewed-By: Colin Ihrig <[email protected]>
Landed in c1a3a98 |
alexfernandez
pushed a commit
to alexfernandez/node
that referenced
this pull request
Nov 1, 2023
- add check for case when trying to provide a better Exception fails - the code was modified to avoid a CHECK_EQ in all cases in nodejs#31076, however, I believe that if we fail to create the exeption to throw instead of simply returning using a CHECK makes more sense. I think it should also address the coverity warning about not initializing in the constructor. Signed-off-by: Michael Dawson <[email protected]> PR-URL: nodejs#49866 Reviewed-By: Colin Ihrig <[email protected]>
targos
pushed a commit
that referenced
this pull request
Nov 11, 2023
- add check for case when trying to provide a better Exception fails - the code was modified to avoid a CHECK_EQ in all cases in #31076, however, I believe that if we fail to create the exeption to throw instead of simply returning using a CHECK makes more sense. I think it should also address the coverity warning about not initializing in the constructor. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #49866 Reviewed-By: Colin Ihrig <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.