Segmentation fault (core dumped),

[ls997...@gmail.com]

When I download the software plink1.9, I tried with "General usage", but there was always a "Segmentation fault (core dumped)", and the software can't run correctly, can you help me?

-rw-r--r-- 1 Shuai Shuai   35147 Jul  5  2016 LICENSE

-rwxr-xr-x 1 Shuai Shuai 6294629 Feb 21 17:17 plink*

-rwxr-xr-x 1 Shuai Shuai   16755 Feb 21 17:17 prettify*

-rw-r--r-- 1 Shuai Shuai      27 Jul  5  2016 toy.map

-rw-r--r-- 1 Shuai Shuai      58 Jul  5  2016 toy.ped

Shuai@DESKTOP-NAA0PUS:~/Shuai/download/plink1.9$ ./plink --file toy --freq --out toy_analysis

PLINK v1.90b5.3 64-bit (21 Feb 2018)           www.cog-genomics.org/plink/1.9/

(C) 2005-2018 Shaun Purcell, Christopher Chang   GNU General Public License v3

Logging to toy_analysis.log.

Options in effect:

  --file toy

  --freq

  --out toy_analysis

Segmentation fault (core dumped)

Shuai@DESKTOP-NAA0PUS:~/Shuai/download/plink1.9$

[Christopher Chang]

Hi,

What operating system are you running on?

[ls997...@gmail.com]

Ubuntu based on windows 10

[Christopher Chang]

That isn’t mature yet. If you want to debug the problem, you’ll need to build from source and e.g. insert debug print statements until you can identify what system call is failing on your machine, because I’m unable to reproduce the issue on my Ubuntu-on-Windows 10 test machine.

Otherwise, download a Windows binary and use that instead.

[ls997...@gmail.com]

Thank you very much for your reply.
I used the subsystem Ubuntu on win10, not the dual system.
I tried another computer in the same way, and it came the same error. There must be something wrong with it.
But the subsystem can run plink2, which is strange.
Now I deleted win10 and reinstalled a complete Ubuntu system in my computer, the plink run correctly.

[Christopher Chang]

To elaborate on my previous comment:

Ubuntu-on-Windows-10 is a work in progress which is mostly but not entirely compatible with regular Ubuntu; some rarer system calls, etc. are not fully emulated on some systems.  plink 1.9 is probably using one of these functions in an unsupported manner.  However, I have a Ubuntu-on-Windows-10 test machine, and plink 1.9 does *not* crash there, so I'd need help in identifying the problematic function call; it's not practical for me to keep buying more Windows machines with different configurations until I find one that reproduces the problem.

With that said, if plink 2.0 actually works on all the Ubuntu-on-Windows-10 subsystems while plink 1.9 segfaults before printing "xxxx MB RAM detected", that greatly reduces the set of possible causes.  If you can post the .log file from one of the failing plink 1.9 runs, that might be enough for me to guess what the problem is and find a workaround.