PowerShell causes Segmentation Fault with Find-Command on Linux when network is connected through VPN

[SteveL-MSFT]

From @hsaito on September 25, 2016 22:5

Steps to reproduce

1. Start Powershell
2. Prompt is displayed
3. Type in Find-Command
4. A segmentation fault occurs

Expected behavior

It should not cause a segmentation fault, and should display a list of commands.

strace below:

PS /home/hideki>                           Find-Command                                                                                                                                               
) = 0
futex(0x93c188, FUTEX_WAKE_PRIVATE, 1)  = 0
gettid()                                = 28897
clone(child_stack=0x7f74317b8fb0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7f74317b99d0, tls=0x7f74317b9700, child_tidptr=0x7f74317b99d0) = 28917
sched_getparam(28917, [0])              = 0
sched_getscheduler(28917)               = 0 (SCHED_OTHER)
sched_get_priority_max(SCHED_OTHER)     = 0
sched_get_priority_min(SCHED_OTHER)     = 0
sched_setscheduler(28917, SCHED_OTHER, [0]) = 0
write(168, "*", 1)                      = 1
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
futex(0x93c1b4, FUTEX_WAIT_PRIVATE, 9, NULL <unfinished ...>
+++ killed by SIGSEGV +++
zsh: segmentation fault  strace powershell

Actual behavior

Powershell segfaults and does not display a list of commands.

Environment data

Name                           Value                                                                                                                                                                 
----                           -----                                                                                                                                                                 
PSVersion                      6.0.0-alpha                                                                                                                                                           
PSEdition                      Core                                                                                                                                                                  
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                                                                                               
BuildVersion                   3.0.0.0                                                                                                                                                               
GitCommitId                    v6.0.0-alpha.10                                                                                                                                                       
CLRVersion                                                                                                                                                                                           
WSManStackVersion              3.0                                                                                                                                                                   
PSRemotingProtocolVersion      2.3                                                                                                                                                                   
SerializationVersion           1.1.0.1     

Copied from original issue: PowerShell/PowerShell#2356

[SteveL-MSFT]

From @MaximoTrinidad on September 25, 2016 23:4

Hi hsaito!

You missed to provide which version of linux you had this issue.

I did ran Find-Command on my Ubuntu 16.04.1 LTS Desktop and had no problems executing the Find-Command in PowerShell version v6.0.0-alpha.10.

. (see image)

[SteveL-MSFT]

From @hsaito on September 26, 2016 8:42

Sorry for the lack of info on that, it's ubuntu 16.04 LTS, 15.6GiB memory, Intel Core i7-2600 CPU @ 340GHz x 8, Gallium 0.4 and AMD TURKS (DRM 2.43.0, LLVM 3.8.0).

I have actually isolated this issue to only happen when I am connected through VPN. If I disconnect from the VPN (OpenVPN -- I can't provide too much detail about its connection due to security issues), it works as designed.

Also noted other commands like Find-Package seems to work over VPN, however observing consistent failure for Find-Command.

[SteveL-MSFT]

From @andschwa on September 29, 2016 18:19

@hsaito can you run the Pester tests and see which fail? That might help to narrow it down.

[SteveL-MSFT]

From @hsaito on September 30, 2016 6:17

I am not sure how the Pester test works at this moment, but does the following output suffice?

./Pester.Tests.ps1
Describing Pester manifest and changelog
[+] has a valid manifest 40ms
[+] has a valid name in the manifest 13ms
[+] has a valid guid in the manifest 13ms
[+] has a valid version in the manifest 14ms
[+] has a valid version in the changelog 19ms
[+] changelog and manifest versions are the same 10ms
Describing Clean treatment of the $error variable
Context A Context
[+] Performs a successful test 30ms
[+] Did not add anything to the $error variable 21ms
Describing SafeCommands table
[+] The SafeCommands table contains all commands that are called from the module 33ms
Describing Style rules
[+] Pester source files contain no trailing whitespace 79ms
[+] Pester Source Files all end with a newline 9ms
Describing ResolveTestScripts
[+] Resolves non-wildcarded file paths regardless of whether the file ends with Tests.ps1 61ms
[-] Finds only *.Tests.ps1 files when the path contains wildcards 19ms
Expected: {True}
But was: {False}
at line: 187 in /home/hideki/pester/Pester/Pester.Tests.ps1
187: ($paths -contains "$TestDrive\SomeFile.Tests.ps1") | Should Be $true
[-] Finds only *.Tests.ps1 files when the path refers to a directory and does not contain wildcards 19ms
Expected: {True}
But was: {False}
at line: 198 in /home/hideki/pester/Pester/Pester.Tests.ps1
198: ($paths -contains "$TestDrive\SomeFile.Tests.ps1") | Should Be $true
[+] Assigns empty array and hashtable to the Arguments and Parameters properties when none are specified by the caller 21ms
Context Passing in Dictionaries instead of Strings
[+] Allows the use of a "P" key instead of "Path" 31ms
[+] Allows the use of an "Arguments" key in the dictionary 16ms
[+] Allows the use of an "Args" key in the dictionary 14ms
[+] Allows the use of an "A" key in the dictionary 16ms
[+] Allows the use of a "Parameters" key in the dictionary 16ms
[+] Allows the use of a "Params" key in the dictionary 20ms
[+] Throws an error if no Path is specified 15ms
[+] Throws an error if a Parameters key is used, but does not contain an IDictionary object 16ms

[mi-hol]

A moved issue seems to become 'orphaned' easily.
Tried to get feedback from author by posting on closed original issue.

'@hsaito with several new version of PSGet published since the bug was reported I wonder if it still exists.
Would you mind to test and comment on PowerShell/PowerShellGet#20 ?'

[edyoung]

This has nothing to do with powershellget. If nobody else has been able to repro and we haven't heard from the original reporter I think it's time to close this

[hsaito]

Sorry for the lack of response. As of 6.0.4, I have observed this is no longer happening.

Thank you.