Segmentation fault (Core Dump)
See original GitHub issueOs: 5.10.42-1-MANJARO
installed dotnet 5 sdk from snap, when I try to run run any command except --version a segmentation fault is thrown
doing export DOTNET_CLI_TELEMETRY_OPTOUT=1
then dotnet new
runs, but still it couldn’t resotre or build any projects
my guess is that the snap sandbox interferes with the permissions dotnet needs to run such as accessing ~/.dotnet and ~/.nuget folders
fix: uninstalled the snap version and installed the SDK from the official repository and it worked fine!
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Segmentation Fault in C/C++
The core dump refers to the recording of the state of the program, i.e. its resources in memory and processor. Trying to access...
Read more >what is Segmentation fault (core dumped)? [duplicate]
"Segmentation fault" means that you tried to access memory that you do not have access to. The first problem is with your arguments...
Read more >How to get a core dump for a segfault on Linux
A core dump is a copy of your program's memory, and it's useful when you're trying to debug what went wrong with your...
Read more >Identify what's causing segmentation faults (segfaults)
Segfaults are caused by a program trying to read or write an illegal memory location. Program memory is divided into different segments: a...
Read more >Segmentation Fault Core Dumped Ubuntu
Segmentation fault is when our system attempts to access any page of memory that does not exist. Core dumped defines when a code...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, @tarekgh, good call to double check. Based on the info provided in the issue it seems like it is:
I will close this as a dupe of: https://github.com/dotnet/runtime/issues/54148 since the other one has more information.