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
8311104: dangling-gsl warning in libwixhelper.cpp #15044
8311104: dangling-gsl warning in libwixhelper.cpp #15044
Conversation
👋 Welcome back asemenyuk! A progress list of the required criteria for merging this PR into |
@sashamatveev please review |
@alexeysemenyukoracle The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
@@ -72,10 +72,10 @@ class ProductInfo { | |||
|
|||
void findInstalledProducts(const Guid& upgradeCode, | |||
std::vector<ProductInfo>& products) { | |||
const LPCTSTR upgradeCodeStr = upgradeCode.toMsiString().c_str(); | |||
const tstring upgradeCodeStr = upgradeCode.toMsiString(); |
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.
I am not familiar with this warning. Does it mean that in original const LPCTSTR upgradeCodeStr = upgradeCode.toMsiString().c_str();
, tstring
retuned from toMsiString()
will get destroyed right after c_str()
completed? Which will make upgradeCodeStr
invalid?
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.
Yep, that is correct
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.
Looks good.
@alexeysemenyukoracle This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 0ca2bfd.
Your commit was automatically rebased without conflicts. |
@alexeysemenyukoracle Pushed as commit 0ca2bfd. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15044/head:pull/15044
$ git checkout pull/15044
Update a local copy of the PR:
$ git checkout pull/15044
$ git pull https://git.openjdk.org/jdk.git pull/15044/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15044
View PR using the GUI difftool:
$ git pr show -t 15044
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15044.diff
Webrev
Link to Webrev Comment