Re: Guile HEAD on Cygwin-1.7

[Andy Wingo]

Hi szgyg,

On Sat 27 Jun 2009 15:36, szgyg <address@hidden> writes:

> Andy Wingo wrote:
>> On Thu 18 Jun 2009 09:33, szgyg writes:
>>> make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build/module'
>>> GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guile-tools compile -o 
>>> "ice-9/psyntax-pp.go" "../../module/ice-9/psyntax-pp.scm"
>>> wrote `ice-9/psyntax-pp.go'
>>
>> I wonder why it's regenerating psyntax-pp.scm. It shouldn't, psyntax.scm
>> should be newer than psyntax-pp.scm.
>
> Git doesn't preserve timestamps, so either file can be the newer after a
> fresh checkout.

Ah, I didn't know this. Hmm, this is a problem. Perhaps we need some
auxiliary Makefile help to make sure psyntax-pp is seen as fresh after a
fresh checkout.

> --- 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? What were your CFLAGS when
compiling Guile?

> in
> commit e33779e3b84b4822b4d51562d7c4f1e65408151d
> Date:   Thu Jun 25 23:24:57 2009 +0100
>     Revert "* FAQ: New file."
>
> 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"?

>>> make[1]: Entering directory `/home/szgyg/src/GIT/guile/=build'
>>> make  check-TESTS
>>> make[2]: Entering directory `/home/szgyg/src/GIT/guile/=build'
>>> Testing /home/szgyg/src/GIT/guile/=build/meta/guile ...
>>> with GUILE_LOAD_PATH=/home/szgyg/src/GIT/guile/test-suite
>>> /bin/sh: line 5:  3944 Segmentation fault      (core dumped) ${dir}$tst
>>> FAIL: check-guile
>>
>> To me that looks like a segfault in your shell.

Hmm, I guess not ;-)

> 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.

Andy
-- 
http://wingolog.org/