It's very strange but I see an only one thread. full Backtrace in attach.
2009/3/12 Neil Jerram
> Stanislav Ievlev 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) sto
Hi,
Albert Chin writes:
> On Thu, Mar 12, 2009 at 04:47:49PM -0500, Albert Chin wrote:
>> 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
>>
Hi,
Stanislav Ievlev writes:
> #6 0x2b98cf981eaf in scm_list_1 () from /usr/lib64/libguile.so.17
> #7 0x2b98cf964099 in gdb_maybe_valid_type_p () from
> /usr/lib64/libguile.so.17
All theses `gdb_*' calls are strange. They refer to Guile's GDB
interface, which never got to the point
Andy Wingo writes:
> Hey Neil,
>
> On Thu 12 Mar 2009 01:53, Neil Jerram 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...
>
Hey all,
I went ahead and merged VM to master. Things went fine after a couple of
manual merges, though `(procedure-property apply 'arity)' needs some
work -- see the log for 5442b3a5989a118f2addf3190eab2e27d65e0658.
I should be happy but really I'm just tired ;) Can people please check
this out,
