I have installed swift3 on my ubuntu machine and when i try to execute any swift code it is giving an error Segmentation fault (core dumped), can anyone tell me what this issue is and how to fix.
Thanks.
Prabu Dass R.
I got the same issue "Segmentation fault (core dumped)" when I'm calling API built by "perfect web framework" using Swift 3 on Ubuntu
16.04 with Postgres Database.
And I've also tried to use "Swift 3.0", "Swift 3.0.1" to build the swift files for test. But none of them work until I tried "Swift 3.0.2 Preview 1" - "https://swift.org/builds/swift-3.0.2-preview-1/ubuntu1604/swift-3.0.2-PREVIEW-1/swift-3.0.2-PREVIEW-1-ubuntu16.04.tar.gz", then it worked! Share with you.
Also list the version I got for swift --version:
Swift version 3.0.2 (swift-3.0.2-PREVIEW-1)
Target: x86_64-unknown-linux-gnu
See that you have +r for all the swift files.
For example in my case [1], I just extracted the files [2] under / and when I tried to execute the 1 + 2 example [3] inside the swift shell, there was a segmentation fault.
This fix was to add read rights for all users with:
cd /usr/lib/swift && sudo chmod -R +r *
[1] Ubuntu 16.04.1, amd64
[2] https://swift.org/download/#previews
[3] https://swift.org/getting-started/#using-the-repl
Related
I am trying to install vscode/vscodium on an asahi ARM operating system (On my Macbook Pro M1). More about ashai
I've tried installing several repositories like this one: https://aur.archlinux.org/packages/visual-studio-code-bin.
Even a Chinese version that is compatible in aarch64: https://www.cxybb.com/article/qq_36154886/109362534
Every time I try to run the program from the terminal with the command .code I get the following error:
/usr/bin/vscodium: line 53: 8741 Segmentation fault ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" --ms-enable-electron-run-as-node "$#"
Honestly, I'm pretty sure I've correctly installed the package with the correct version for my computer's architecture but I don't know how I could solve the problem, online there are no results.
Thanks!
I am trying to build this project using Rust on WSL. However, after running npm run build:program-rust my computer crashed and showed a BSD (I caused the crash twice to make sure this command was the actual cause).
What is the workaround for this issue?
Thanks to the discussion on this issue I realized I was on WSL 1 (you can check with wsl -l -v)
I tried migrating my Ubuntu 20.04 instance to WSL 2 by running wsl --set-version <my_distro_name> 2 and it appears to have resolved the Blue Screen issue.
I've downloaded Realm Studio from here. When I opened for the first time it asked me if I wanted to integrate it into my system. I clicked on Yes and from there nothing. I can't open the App and if I launch it from terminal I see only
segmentation fault (core dumped)
This happens also with version 2.8 and with the .tar version (Nothing happens if I click on the icon in the extracted archive and the same message if I try to run it from the terminal).
I'm running Ubuntu 18.10 64bit. Thank you all for the help.
I'm trying to follow this guide. I'm running both Ubuntu 12.04.5 LTS (GNU/Linux 3.13.0-74-generic x86_64) on "real" hardware and 14.04.1 via VirtualBox on my Mac. The problem is that I don't even get past Step 1:
hoffmann#angl99:~$ export CCPREFIX=/home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-
hoffmann#angl99:~$ ${CCPREFIX}gcc -v
I'm then getting the following error:
-bash: /home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc: No such file or directory
However, the file that I'm told is missing is certainly there:
hoffmann#angl99:~$ less /home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc
"/home/hoffmann/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc" may be a binary file. See it anyway?
This is probably the result of a basic error/misconception. Could anybody suggest a solution?
Thanks!
Sebastian
OK - I've worked it out (with the help of the person who posted the guide I'm trying to follow). It was indeed a basic issue...
The cross compiler binaries I was going to use are 32-bit and I was running a 64-bit system. I've now installed a 32-bit Ubuntu on VirtualBox and everything is running smoothly.
I downloaded and extracted VS Code in a Debian x64 VM and tried to run it. It complained about missing glibc libraries (I have 2.13, it needs 2.15). I followed these steps to get Ubuntu DEBs. Using those, VS Code throws a segmentation fault when I run it. gdb tells me:
linux_test_for_tracefork: waitpid: unexpected status 11.
Why won't Visual Studio Code run for me in my Debian VM?
Updating to Debian 8 fixed this problem.