runtime: Segmentation fault on dotnet [name-of-app].dll on Debian
@ChristianHaase commented on Sun Feb 11 2018
Getting segmentation fault when running the application. Only on HTTP client request sending to external API. The app start fine and I can navigate fine, but whenever I try to login (calling external API), I’m getting the segfault. Same goes for creating a new user, when calling the external API from my MVC backend.
Running the app locally, everything works as expected, and I can login fine, as well as creating a new user.
I have a try/catch around the enitre method, but I’m never hitting the catch. The segfault happens instead of the catch.
Technical details
dotnet --info
.NET Command Line Tools (1.0.4)
Product Information
Version: 1.0.4
Commit SHA-1 hash: afefd
Runtime Environment
OS Name: debian
OS Version: 9
OS Platform: Linux
RID: debian.8-x64
Base Path: /opt/dotnet/sdk/1..4
Is there any fancy way for me te debug, or get some kind of log about what’s happenening?
@Petermarcu commented on Tue Feb 20 2018
@leecow is Debian 9 supported by 1.0?
@leecow commented on Wed Feb 21 2018
No, Debian 9 is 2.0. https://github.com/dotnet/core/blob/master/os-lifecycle-policy.md.
@ChristianHaase commented on Wed Feb 21 2018
I suppose that would explain some issues, but the application runs fine on the server. It’s only remote HTTP request that causes the segfault?
@wfurt commented on Wed Feb 21 2018
What version of curl and openssl do you have? This may be same as dotnet/runtime#23965 and dotnet/runtime#23796 You can try container with supported OS. That should get you around linkage problems.
@ChristianHaase commented on Wed Feb 21 2018
OpenSSL version:
OpenSSL 1.10f 25 May 2017
curl version:
curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
I don’t know what issues you are referring to (#24891 and dotnet/runtime#23796)?
@wfurt commented on Wed Feb 21 2018
oh, the link did not work 😭 https://github.com/dotnet/corefx/issues/24552 and https://github.com/dotnet/corefx/issues/24891
@ChristianHaase commented on Wed Feb 21 2018
I’m trying to convert my project to .NET core 2.0, and updating the installed version on my server. I will update my progress here once done. Thanks for the inputs.
@ChristianHaase commented on Sat Feb 24 2018
I updated the project to 2.0, but it’s still a problem. I’ll take a look at the links you provided @wfurt
@ChristianHaase commented on Sat Feb 24 2018
I looked at the installed version of libcurl, and this is what I could find:
Anything I can do here?
@Petermarcu commented on Sun Mar 11 2018
I’m going to move this to the corefx repo where it will be tracked better.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 24 (12 by maintainers)
No of course not. I apologize. I’m waiting for my server technician to boot up our test environment so I can test the project. I’ll get back to you once I’ve tested it.
I’ll test a simple console application as well, and attach a repro if it fails too.
I created a repro, but I want to test it myself first. I’ve installed a local machine with debian 9, if it fails there, I’ll send you the repro. If not, I’ll test on the AWS debian server, and send you the repro if it fails. I’ll get back to you once I’ve tested myself.