[release/7.0] Move AT_EXECFN to fallback for /proc/self/exe #79057
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #78958 to release/7.0 Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsBackport of #78958 to release/7.0 Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
jeffschwMSFT
added
Servicing-approved
|
Approved by Tactics for 7.0.3. |
ghost
locked as resolved and limited conversation to collaborators
Backport of #78958 to release/7.0
/cc @janvorli @am11
Customer Impact
When building a self-contained console application targeting .NET 7, the console application doesn't work with shebang in Linux. This causes powershell v7.3.0 to stop working with shebang on Linux.
When building the same console application targeting .NET 6, the produced console application works fine with shebang.
Testing
CI coreclr and libraries tests
Risk
Low, the change just swaps the order of means we use for getting the current executable path, the
/proc/self/exeis used first now. And in 6.0, we accidentally were using just the/proc/self/exefor some time, so it was well tested.