Re: Guile HEAD on Cygwin-1.7

2009-06-27 Thread szgyg
Andy Wingo wrote: On Thu 18 Jun 2009 09:33, szgyg writes: ** wrong path when compiling psyntax-pp.scm First time only Making all in module make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build/module' /home/szgyg/src/GIT/guile/=build/meta/guile --no-autocompile -s ../../module/ice-9

Re: Guile HEAD on Cygwin-1.7

2009-07-07 Thread szgyg
Andy Wingo wrote: On Sat 27 Jun 2009 15:36, szgyg writes: --- T.scm --- (define *old-stack-level* (and= (memq 'stack (debug-options)) cadr)) (debug-set! stack (* 2 *old-stack-level*)) (display #t) - $ guile -q --debug -s T.scm Backtrace: In ../../module/ice-9/boot-9.scm: 874: 0

Re: Guile HEAD on Cygwin-1.7

2009-07-25 Thread szgyg
Andy Wingo wrote: 1. psyntax-pp.scm sometimes regenerating itself Yes. 2. some kind of segfault related to stack sizes on cygwin Not segfault, stack overflow after we make the stack bigger with debug-set!. I didn't debugged this yet. 3. The following: That segfault was an fd_set

Re: Cygwin port of Guile 2.2

2017-05-03 Thread szgyg
efore > pthread_join doesn't return until after the key destructors have run. > This is my understanding of what happens from reading NPTL. Do I > understand correctly that you are on Cygwin? Could it be a cygwin > pthreads incompatibility? > > Andy > http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09 2.9.5 Thread Cancellation Thread Cancellation Cleanup Handlers #v+ After all cancellation cleanup handlers and thread-specific data destructors have returned, thread execution is terminated. #v- szgyg

Re: bug#39118: Segfault while building on 64-bit Cygwin

2020-02-05 Thread szgyg
On Wed, Feb 05, 2020 at 04:11:04PM -0500, John Cowan wrote: > On Mon, Feb 3, 2020 at 5:11 PM szgyg wrote: > > On Fri, Jan 31, 2020 at 09:23:19AM -0500, John Cowan wrote: > > > Aaaand... Cygwin doesn't do core dumps. Under the skin it's WIndows, > > after > > >

Re: bug#39118: Segfault while building on 64-bit Cygwin

2020-02-03 Thread szgyg
On Fri, Jan 31, 2020 at 09:23:19AM -0500, John Cowan wrote: > 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: > [...] Please see my previous mail on how to get a real core dump on cygwin

Re: bug#39118: Segfault while building on 64-bit Cygwin

2020-01-21 Thread szgyg
On Tue, Jan 21, 2020 at 10:01:58AM +0100, Ludovic Courtès wrote: > but before that you’d run > “ulimit -c unlimited” in that shell to make sure there’s a core dumped > when it crashes. This won't work on cygwin. If you want a core dump, you should use the dumper tool, as described here