Re: Segfault when running fibc benchmark in current trunk

[Juhani Rantanen]

>> I look forward to the next bug report :)
>
> Here are some more files that don't need the benchmark suite to run. I
> also ran all of the tests with Gambit and there wasn't any errors.
>
> Testing maze under Guile-r5rs
> Compiling...
> Running...
> ERROR: In procedure zero?:
> ERROR: Wrong type argument in position 1: #f

Hi,

I still have some cough and flu, I hope you're luckier and have not
catched this evil disease.. Anyway, as I made this bug report I was sick
so my brain didn't work like normal, as it seems that this maze_bug.scm
not working is actually a portability issue in the testsuite, not a
genuine guile bug. At least this seems likely. Benchmark does run with
Gambit without any errors, but that is a different implementation with
different set of primitives. So I'm sorry if I've sent you to a wild goose
chase.

That aside, I am interested in using Guile to extend my application and I
will volunteer to test it with some other code as well before the next
release to improve quality of the release. I used to do release testing
and Unix/DB administration for a living (maybe that is why I wanted to run
the benchmarks and use a development version in the first place :) but I
don't have too much coding experience (in big sw projects) so I won't do
patches at first unless they are trivial in nature. If all goes well I
will report some more bugs soon. One bug might be that Guile 1.8.6 runs
every benchmark (some of them are real-world applications, some simple
synthetic benchmarks) faster than the current version with this new VM.

BR,
Juhani