clisp segfault

[Hellrespawn]

Windows 10 Pro, version 1803, build 17134.165

I'm trying to run clisp (clisp_2.49.20170913-4build1_amd64) on Ubuntu 18.04 but it's failing with the following message:
Cannot map memory to address 0x8009635c2000
[/build/clisp-u7VYrq/clisp-2.49.20170913/src/spvw_mmap.d:498] errno = 22 (Segmentation fault (core dumped)

The address seems to be random every time.

Strace: https://gist.github.com/Hellrespawn/3af705260bde2e2d760dde9860441d24

As far as I can tell, this is not the same bug as #1128 or #1201 and googling the error message doesn't bring anything up. Any help would be appreciated.

[therealkenc]

Haven't dug deep (no repro, natch) but the mincore(2) fail in the strace log seems pretty clear on this one. Was mentioned in #645 (in passing).

912   mincore(0x80098109f000, 4096, 0x7fffe8847cb7) = -1 ENOSYS (Function not implemented)

[Hellrespawn]

It seems that clisp does work on Ubuntu 16.04. Manually installing clisp_2.49-10build1_amd64.deb and libffcall1_1.10+cvs20100619-4_amd64.deb from the 17.10 repositories in 18.04 works as a workaround, but it's not ideal.

[therealkenc]

Goes to #1128 (message) and (tangentially) #2555 (message). Libsigsegv uses mincore(2). clisp uses libsigsegv. Libsigsegv was created for a relatively uncommon subset of software developers that believe segfaults are a feature not a bug, and one way to implement garbage collectors. [This uncommon subset has been mostly replaced by a new breed that believe allocating a terrabyte of memory up front so nothing ever faults is the answer.] It isn't clear how (or whether) clisp was fixed, or what version was being used at the time. But from what you are saying, speculating, maybe the gaps were patched over upstream (deliberately for WSL or by happenstance I can't say).

[therealkenc]

Hmm. I fired up native Chrome for the first time in many months, and it now (68.0.3440.75) seems to depend on mincore(2) over here too. This causes a constant stream of the following error to be spewed to the console that wasn't present last time I poked around:

process_memory_dump.cc(159)] CountResidentBytes failed. The resident size is invalid

So call it another use case. Hope mincore() is "doable".

[webanck]

Windows 10 Famille, version 1903, build 18362.418
WSL's Ubuntu 18.0.4.3

I get a clisp error, trying to compile a Latex document with pdflatex calling makeglossaries calling xindy using clisp.

xindy  -L french -C utf8 -I xindy -M "main" -t "main.xxx-glg" -o "main.xxx-gls" "main.xxx-glo"
Cannot map memory to address 0x80098aeb1000 .

***Call to xindy failed***

Check 'main.implicits-glg' for details
[/build/clisp-u7VYrq/clisp-2.49.20170913/src/spvw_mmap.d:498] errno = 12

I get the same clsp error calling xindy --version:

xindy release: unknown
xindy script version: 1.18
Cannot map memory to address 0x80097240d000 .
[/build/clisp-u7VYrq/clisp-2.49.20170913/src/spvw_mmap.d:498] errno = 12

[supernovae]

Ubuntu 18.0.4 Windows 10 1909

bmiller@SP4:/mnt/c/Users/mtheo$ clisp -repl Cannot map memory to address 0x80096ced6000 . [/build/clisp-u7VYrq/clisp-2.49.20170913/src/spvw_mmap.d:498] errno = 12 (Segmentation fault (core dumped

[michaelkolber]

@therealkenc Any update on this issue? I'm getting the same error as @supernovae, same specs.

[therealkenc]

You should be good on WSL2.