Re: Segfault while building on 64-bit Cygwin

2020-02-17 Thread Andy Wingo
Aah, you all are amazing -- thank you!! Applied and merged. Cheers, Andy On Mon 17 Feb 2020 20:27, Charles Stanhope writes: > On 2/16/20, Charles Stanhope wrote: >> On 2/16/20, Mike Gran wrote: >>> >>> I can confirm that Charles's patch, plus another one line patch >>> to define

Re: Segfault while building on 64-bit Cygwin

2020-02-17 Thread Charles Stanhope
On 2/16/20, Charles Stanhope wrote: > On 2/16/20, Mike Gran wrote: >> >> I can confirm that Charles's patch, plus another one line patch >> to define CPU_SETSIZE, is enough to get Guile 3.0.x to build and run >> on my box. All tests pass except strptime in French, and the absence >> of crypt.

Re: Segfault while building on 64-bit Cygwin

2020-02-16 Thread Charles Stanhope
On 2/16/20, Mike Gran wrote: > On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote: >> Andy, I don't know if you'd want to continue this here or on >> lightening's gitlab page, but I looked into this a little bit a few >> minutes here and there this past weeek. The x86 "fast-call"

Re: Segfault while building on 64-bit Cygwin

2020-02-16 Thread John Cowan
Excellent, and thank you all! I've been WIndowsless for a few weeks, but that should change again soon. On Sun, Feb 16, 2020 at 6:23 PM Mike Gran wrote: > On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote: > > Andy, I don't know if you'd want to continue this here or on > >

Re: Segfault while building on 64-bit Cygwin

2020-02-15 Thread Marco Atzeri
Am 14.02.2020 um 18:46 schrieb Charles Stanhope: On 2/6/20, Charles Stanhope wrote: On 2/6/20, Andy Wingo wrote: Given that John said that compilation went fine with GUILE_JIT_THRESHOLD=-1, I think perhaps this problem may have been fixed in the past. My suspicions are that this issue is

Re: Segfault while building on 64-bit Cygwin

2020-02-14 Thread Charles Stanhope
On 2/6/20, Charles Stanhope wrote: > On 2/6/20, Andy Wingo wrote: > >> Given that John said that compilation went fine with >> GUILE_JIT_THRESHOLD=-1, I think perhaps this problem may have been fixed >> in the past. My suspicions are that this issue is an ABI issue with >> lightening that could

Re: Segfault while building on 64-bit Cygwin

2020-02-06 Thread Charles Stanhope
On 2/6/20, Andy Wingo wrote: > Given that John said that compilation went fine with > GUILE_JIT_THRESHOLD=-1, I think perhaps this problem may have been fixed > in the past. My suspicions are that this issue is an ABI issue with > lightening that could perhaps be reproduced by: > > git co

Re: Segfault while building on 64-bit Cygwin

2020-02-06 Thread Andy Wingo
On Mon 20 Jan 2020 18:22, Mike Gran writes: > On Mon, Jan 20, 2020 at 11:38:35AM -0500, John Cowan wrote: >> Yes, gladly, but I don't know how to get one in this context. Do I need to >> add some flags to the Makefile, and if so, where? (It's a twisty maze of >> passages, all different.) .

Re: Segfault while building on 64-bit Cygwin

2020-01-31 Thread John Cowan
Aaaand... Cygwin doesn't do core dumps. Under the skin it's WIndows, after all. This is what I get when I specify ulimit -c unlimited and rebuild: Exception: STATUS_ACCESS_VIOLATION at rip=0055A8B1B25 rax= rbx=FF90 rcx=FF90 rdx=0034964A

Re: Segfault while building on 64-bit Cygwin

2020-01-25 Thread Ludovic Courtès
John Cowan skribis: > Both Cygwin and MacOS crash in pretty much the same way. By disabling the > JIT, I was able to get the Cygwin build to run to completion. That I understand. However, I was asking for the backtrace of the crash on Cygwin when JIT is enabled. Could you grab it? Thanks in

Re: Segfault while building on 64-bit Cygwin

2020-01-24 Thread John Cowan
Both Cygwin and MacOS crash in pretty much the same way. By disabling the JIT, I was able to get the Cygwin build to run to completion. On MacOS with --disable-jit, however, I am now getting an entirely new failure: CC readline.lo readline.c:432:7: warning: implicitly declaring library

Re: Segfault while building on 64-bit Cygwin

2020-01-23 Thread Ludovic Courtès
Hi, John Cowan skribis: > Thanks. Unfortunately, the standard recipe for making core dumps on Mac This bug report is about Cygwin, not macOS, right? :-) Ludo’.

Re: Segfault while building on 64-bit Cygwin

2020-01-21 Thread John Cowan
Thanks. Unfortunately, the standard recipe for making core dumps on Mac (put "limit core unlimited" into /etc/launchd.conf and reboot, make sure /cores is writable, set ulimit -c unlimited) seem to actually enable them on MacOS Catalina (10.15.2). I have tested with SIGQUIT and SIGSEGV on

Re: Segfault while building on 64-bit Cygwin

2020-01-21 Thread Ludovic Courtès
Hello, John Cowan skribis: > Yes, gladly, but I don't know how to get one in this context. You would unpack, configure, and build like you did before (with JIT enabled, so as to reproduce the crash), but before that you’d run “ulimit -c unlimited” in that shell to make sure there’s a core

Re: Segfault while building on 64-bit Cygwin

2020-01-20 Thread John Cowan
Yes, gladly, but I don't know how to get one in this context. Do I need to add some flags to the Makefile, and if so, where? (It's a twisty maze of passages, all different.) . Note that this *is* a build with JIT enabled; when I disable it using the env variable, there are no errors and 3.0.0