Greetings!
On my 2.6.18 kernel guile (latest snapshot from git, branch-release-1.8
head) in some situations (unfortunately I can't made a testcase) stops
forever. Guile with 2.6.27 kernel works well.
Strace:
futex(0xc571890, FUTEX_WAIT, 2, NULL...
Backtrace:
--
#0 0x2b4ba31b4004 in
I've built guile-1.8.6 on HP-UX 11.23/IA and 11.31/IA:
$ gtar zxf guile-1.8.6.tar.gz
$ cd guile-1.8.6
$ ./configure PTHREAD_CFLAGS=-mt --disable-dependency-tracking
...
$ gmake
$ ./check-guile r4rs.test
Testing /opt/build/china/guile-1.8.6/pre-inst-guile ... r4rs.test
with
Stanislav Ievlev stanislav.iev...@gmail.com writes:
Greetings!
On my 2.6.18 kernel guile (latest snapshot from git, branch-release-1.8 head)
in some situations (unfortunately I can't made a testcase) stops forever.
Guile
with 2.6.27 kernel works well.
Strace:
futex(0xc571890,
Andy Wingo wi...@pobox.com writes:
How much of this is compiler-specific? Does some of it also apply to
old-style reading and interpreting?
No, it's just compiler-specific. The reader captures source information
at when it reads lists, as you know, and this is just propagating more
of it.
Albert Chin guile-de...@mlists.thewrittenword.com writes:
Core was generated by `guile'.
Program terminated with signal 11, Segmentation fault.
SEGV_ACCERR - Invalid Permissions for object
I've never seen that (SEGV_ACCERR) before. Do you know what it means?
Neil
Hey Neil,
On Thu 12 Mar 2009 01:53, Neil Jerram n...@ossau.uklinux.net writes:
Thanks to a hint from helgrind, I think the problem might be that the
symbols obarray is not thread-safe. But surely using a mutex for
every symbol that Guile reads would be terrible for performance...
Dunno, in
