Skip to content

[6.1.0]Use long executable path instead of argv[0] in all launchers#17272

Merged
ShreeM01 merged 3 commits intobazelbuild:release-6.1.0from
ShreeM01:ks/cherry-pick16916
Jan 20, 2023
Merged

[6.1.0]Use long executable path instead of argv[0] in all launchers#17272
ShreeM01 merged 3 commits intobazelbuild:release-6.1.0from
ShreeM01:ks/cherry-pick16916

Conversation

@ShreeM01
Copy link
Copy Markdown
Contributor

argv[0] can differ from the path of the launcher executable. The latter can contain 8.3 style filenames, which need to be resolved to long paths before path manipulation (e.g. appending ".runfiles") can succeed.

The Python launcher handled this correctly, but other launchers didn't use the long executable path consistently.

Closes #16916.

PiperOrigin-RevId: 493615543
Change-Id: Ic8161890181c0110ecdf6893b9835e6f99d01097

`argv[0]` can differ from the path of the launcher executable. The latter can contain 8.3 style filenames, which need to be resolved to long paths before path manipulation (e.g. appending ".runfiles") can succeed.

The Python launcher handled this correctly, but other launchers didn't use the long executable path consistently.

Closes #16916.

PiperOrigin-RevId: 493615543
Change-Id: Ic8161890181c0110ecdf6893b9835e6f99d01097
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants