question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Too many files are marked executable

See original GitHub issue

Too many files are marked executable. (while I’ve only looked at the osx-arm64 build, I would guess this is a general problem.

% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f | wc -l   
     498

The reasonable set of executable binaries would be these. (apphost and singlefilehost templates are debatable).

steve@Toms-Mac-2 helloWorld % find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -not '(' -name \*.dll -o -name \*.dylib -o -name \*.xml -o -name \*.txt -o -name \*.a -o -name \*.h ')'
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/shared/Microsoft.NETCore.App/6.0.0-alpha.1.20624.8/createdump
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/dotnet
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.NETCore.App.Host.osx-arm64/6.0.0-alpha.1.20624.8/runtimes/osx-arm64/native/apphost
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.NETCore.App.Host.osx-arm64/6.0.0-alpha.1.20624.8/runtimes/osx-arm64/native/singlefilehost
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/sdk/6.0.100-alpha.1.20625.2/AppHostTemplate/apphost

We are marking dll, xml, dylib, txt, h and a extensions executable. None of these represent executable programs.

% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.dll | wc -l   
     318
% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.xml | wc -l 
     153
% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.dylib | wc -l 
      14
% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.txt | wc -l 
       4
% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.h | wc -l 
       3
% find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f -name \*.a | wc -l 
       1

This issue probably belongs in another repo (arcade?), but symptoms cross dependent repos

 % for i in $(find ../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64 -perm +111 -type f '(' -name \*.dll -o -name \*.dylib -o -name \*.xml -o -name \*.txt -o -name \*.a -o -name \*.h ')' | sort -f ); do dirname $i; done | sort -f | uniq
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/host/fxr/6.0.0-alpha.1.20624.8
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.AspNetCore.App.Ref/6.0.0-alpha.1.20624.2/data
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.AspNetCore.App.Ref/6.0.0-alpha.1.20624.2/ref/net6.0
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.NETCore.App.Host.osx-arm64/6.0.0-alpha.1.20624.8/runtimes/osx-arm64/native
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.NETCore.App.Ref/6.0.0-alpha.1.20624.8/data
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/Microsoft.NETCore.App.Ref/6.0.0-alpha.1.20624.8/ref/net6.0
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/NETStandard.Library.Ref/2.1.0/data
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1
../dotnet-sdk-6.0.100-alpha.1.20625.2-osx-arm64/shared/Microsoft.NETCore.App/6.0.0-alpha.1.20624.8

/cc @jkoritzinsky @ViktorHofer @mmitche

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
dagoodcommented, Jan 7, 2021

Oh… right. 😄 Well, the nupkgs (Microsoft.NETCore.App.Host.osx-arm64) don’t persist permission bits and NuGet restore extracts them as 744, which matches. I guess the SDK layout uses the nupkgs, not the tar.gzs.

0reactions
dagoodcommented, Oct 27, 2021

This hasn’t changed. Here’s a fresh screenshot of dotnet-sdk-6.0.100-osx-arm64.tar.gz packs\Microsoft.NETCore.App.Host.osx-arm64\6.0.0\runtimes\osx-arm64\native\:

image

Read more comments on GitHub >

github_iconTop Results From Across the Web

linux - Why are so many of my files executable?
Many of the files in my home directory are executable for no good reason. By 'executable' I mean that the -x flag is...
Read more >
All files on automounted NTFS partition are marked as ...
Because any file I create on or move to the partition is automatically marked as executable. The problem is that there is no...
Read more >
All my files, from Windows, are executable - Support
Hi Manjaro forum, All my files (jpg, docs, txt, pdf etc) that I have copied from my windows harddrive, are marked as executable....
Read more >
All files on /mnt/drive_letter are marked as executable · ...
All files in Windows accessed from Linux subsystem are marked with 'x' bit. Files such as .txt are not executable.
Read more >
ls -F/--classify marks every file as an executable
ls -F classifies ALL files on my mounted partitions as an executable (it appends an asterisk to the end of the file name)....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found