New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation Fault - Raspbian ARM v6.0.0-rc.2 #5696
Comments
What OS distro and version are you using? Only Raspbian Stretch is currently supported on R-Pi2/3. |
I was using Raspberry Pi 1 and jessie. I then updated to stretch. It worked when I used RP 3 |
After being idle for a few moments, it then does the segmentation fault. pi@xxx:~ $ date https://aka.ms/pscore6-docs PS /home/pi> Segmentation fault |
The same happens here on a RP3, with Raspian stretch pi@raspberrypi2:~ $ ~/powershell/pwsh https://aka.ms/pscore6-docs PS /home/pi> date
|
This isn't repro'ing for me on rc2. Can one of you use gdb and get a stack trace when it crashes? |
Hi Steve,
Sorry, can't repro anymore either. Did a clean install of Raspian Stretch
and it worked directly.
I got the error after an in-place upgrade from Raspian Jessie to stretch.
So it's probably related to something already installed.
Sorry I can't be of more assistance.
Cheers,
Rex
Op 2 jan. 2018 8:20 p.m. schreef "Steve Lee" <notifications@github.com>:
… This isn't repro'ing for me on rc2. Can one of you use gdb and get a stack
trace when it crashes?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5696 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHpLW3qy50yC4GsK07gVkccusuAce48eks5tGoGBgaJpZM4RDAB8>
.
|
i am still getting the segmentation fault. Will need instruction on how to do the gdb. |
@minoseah629 , looks like you are trying to run on Raspberry Pi 1 ('Environment data' in original post shows 'armv6l'). |
The initial post was Rpi1, but after getting the note about stretch. I installed stretch on Rpi3. I closed the item but saw it still happened after RPi 3 so I reopened the issue @SteveL-MSFT @anmenaga |
@minoseah629 Interesting. Did you install any other apps/packages on that RPi 3 where segmentation fault happens, or is it a 'clean' Raspbian Stretch? |
it was not clean install. I wanted to keep some files. here is a list of my installed apps:
|
@minoseah629 can you collect a stacktrace? sudo apt-get install gdb
gdb pwsh
# you'll see debug spew from gdb, just ignore it
# get a segmentation fault
backtrace |
Looks like something is wrong on upgrades...
On the other hand, www.raspberrypi.org recommends using clean Stretch images:
|
here is a recording of the gdb. i dont know how to use the gdb so i did a search and saw backtrace as a command. let me know what commands that would be helpful to use. http://www.screencast.com/t/hd3iICu5 video of repro |
@minoseah629 When you get "(gdb)" prompt try "run". |
|
|
@minoseah629 Can you please try these 2 things on that RPI3:
|
output for #1:
output for #2:
|
hello, just an update. still getting this error on v6.0.1 |
What is the output of |
gdb ~/powershell/pwsh --q https://aka.ms/pscore6-docs [New Thread 0x6b6d0450 (LWP 1967)] Thread 10 "pwsh" received signal SIG34, Real-time event 34. |
I'm seeing the same thing on RP3 after recently upgrading from jessie to stretch. Haven't tried a clean install of stretch. pwsh launches and I might be able to get one command off, but shortly after it will report "Segmentation fault" and exit even if I don't execute a command. |
At this point, since support on ARM is experimental, I would recommend going with a clean install as it may not be worth the effort to investigate upgrade issues. |
Confirmed that it works fine on a clean install of stretch on my RP3. |
I had this same problem on my RP3 with Raspbian jessie installed. I upgraded my distro as per the steps here -> jessie to stretch which afterwards PowerShell was working. |
Yep, this is an RP3 issue. Look at all the repros (I am hitting this on a new build). Everyone has a Rpi3. @joeyaiello @SteveL-MSFT
|
Interesting
|
Yep, looks clearly that it's the libcrypto.so.1.0.0 issue. So CoreCLR is loading 1.0.0 and not 1.0.2, and the upgrade to Stretch from Jessie didn't clean up. I'm doing this, and will report back:
|
@dantraMSFT Should we create a soft link on right libcrypto version in installer? |
this issue appears to be resolved with 6.1
|
Stumbled on this when searching for the same error text. For what it is worth, I'm not using PowerShell nor a RPi, but also Debian Stretch on an ARM i.MX6 embedded device (32bit). So, perhaps it is a libcryptopp ARM related issue (word size?). |
Steps to reproduce
https://github.com/PowerShell/PowerShell/blob/master/docs/installation/linux.md#raspbian
Expected behavior
Powershell should start
Actual behavior
I get segmentation fault and powershell does not start.
Environment data
The text was updated successfully, but these errors were encountered: