Re: Guile HEAD on Cygwin-1.7

[szgyg <szgyg@ludens.elte.hu>]

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* [#<program 100d7500 ()>]
>> In unknown file:
>>    ?: 1* [primitive-load "T.scm"]
>> In ../../module/ice-9/psyntax-pp.scm:
>> 8216: 2* [# #]
>>
>> ERROR: Stack overflow
> 
> Interesting. Is this the full backtrace?

Yes.

> What were your CFLAGS when
> compiling Guile?

My CFLAGS is empty, configure sets to -g -O2.

>> The stack can grow a little, but not so much. Works with the factor 1.3,
>> but not with 1.4 (*old-stack-level* is  416784).
> 
> I don't understand -- do you mean to say that T.scm works if "(* 2" is
> replaced with "(* 1.3"?

Yes, with "(inexact->exact (floor (* 1.3".

-----

>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to thread 3544.0xc1c]
>> 0x6aac70d9 in scm_read_delimited_x (delims=0x100e6400, str=0x102f90a0,
>>     gobble=0x104, port=0x102bd398, start=0x204, end=0x204)
>>     at ../../libguile/inline.h:307
>> 307           if (scm_fill_input (port) == EOF)
> 
> What exactly is segfaulting here? All of the vars look fine, and in your
> printouts.
> This seems just to be a problem running Guile, perhaps not
> specific to the tests. Can you run meta/guile and it works? If not,
> meta/gdb-uninstalled-guile might be useful.

Thanks, `./check-guile -i meta/gdb-uninstalled-guile foo.test' is pretty 
cool.

That segfault was an fd_set overflow. We should
#define FD_SETSIZE 1024
before including sys/types.h on cygwin. Also, guile should check that 
  (filedescriptor < FD_SETSIZE) before FD_SET and select.

s