dotnet restore/dotnet run in the 1.0 CLI fail with a segmentation fault on debian stretch
See original GitHub issueFrom @livarcocc on April 14, 2017 20:21
From @harindu95 on March 26, 2017 2:25
Steps to reproduce
I tried the following method from official site.
sudo apt-get install curl libunwind8 gettext
curl -sSL -o dotnet.tar.gz https://go.microsoft.com/fwlink/?linkid=843453
sudo mkdir -p /opt/dotnet && sudo tar zxf dotnet.tar.gz -C /opt/dotnet
sudo ln -s /opt/dotnet/dotnet /usr/local/bin
dotnet new console -o hwapp
Expected behavior
Creating a new project
Actual behavior
Crashed with the following error
Error reading JObject from JsonReader. Path '', line 0, position 0.
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json)
at Microsoft.TemplateEngine.Edge.Settings.SettingsLoader.EnsureLoaded()
at Microsoft.TemplateEngine.Edge.Settings.SettingsLoader.GetTemplates(HashSet`1 templates)
at Microsoft.TemplateEngine.Edge.Template.TemplateCreator.List(Boolean exactMatchesOnly, Func`3[] filters)
at Microsoft.TemplateEngine.Cli.New3Command.PerformCoreTemplateQueryAsync()
at Microsoft.TemplateEngine.Cli.New3Command.<EnterTemplateManipulationFlowAsync>d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Microsoft.TemplateEngine.Cli.New3Command.<ExecuteAsync>d__66.MoveNext(\'
Environment data
dotnet --info output:
.NET Command Line Tools (1.0.1)
Product Information:
Version: 1.0.1
Commit SHA-1 hash: 005db40cd1
Runtime Environment:
OS Name: debian
OS Version: 9
OS Platform: Linux
RID: debian.8-x64
Base Path: /opt/dotnet/sdk/1.0.1
find /opt/dotnet -name ‘*.so’ -type f -print | xargs ldd | grep ‘not found’
liblldb-3.6.so => not found
liblldb-3.6.so => not found
Copied from original issue: dotnet/cli#6153
Copied from original issue: dotnet/templating#589
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (12 by maintainers)
Top Results From Across the Web
Segmentation Fault Error upon running dotnet new console ...
Description: Restore NuGet packages required by this project. Manual instructions: Run 'dotnet restore' Segmentation fault (core dumped).
Read more >Troubleshoot .NET tool usage issues
NET tool fails to run, most likely you ran into one of the following issues: The executable file for the tool wasn't found....
Read more >Segfault when running a console app using the dotnet-cli
I tried everything in my power, it works fine locally but always fails with error-code 139 when running in travis-ci. The console-app currently ......
Read more >Bug listing with status RESOLVED with resolution TEST- ...
1.4.1) segmentation fault'ed while starting up" status:RESOLVED resolution:TEST-REQUEST severity:normal · Bug:29841 - "ebuild request: "SiteBar": bookmark ...
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
(was: =dev-java/jdbm-1.0 is available)" status:RESOLVED resolution:OBSOLETE ... Bug:337660 - "net-dialup/wvdial-1.61 Segmentation fault" status:RESOLVED ...
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
I guess a VM running Debian Jessie will be needed if I want to develop with .NET core for now, but the point of dotnet core was to avoid using a VM to do .NET development
I actually managed to use .NET Core 1.0 on Stretch using some Jessie package.
I have detailed it here.
I guess I’ll try 2.0 when it’ll be released.