I've put in a cumulative of 36 hours guile-2.9.2 multi-threaded stress
testing on two different OS/compiler/glibc combinations, and have seen
exactly zero crashes or hangs so far. So it's perfect. Sorry for earlier
confusion. -- linas
On Sun, May 26, 2019 at 11:40 PM Linas Vepstas
wrote:
> Andy
Andy,
I want to temporarily, maybe permanently retract my last email. I found a
bug(let) in the intialization of my unit test that appears to maybe account
for all observed crashes, maybe. I'm re-verifying on multiple machines but
this will take 24-48 hours. Basically, it looks like guile-2.9.2 i
Hi Andy,
Thanks! I just tried out the master branch of guile in git (the one tagged
v2.9.2). It now passes all of my unit tests. So that's good! ... More or
less -- there's still some infrequent multi-threading bug(s). Let me
describe.
My unit test just transitions C->guile->C and returns, in
Hi!
On Thu 06 Dec 2018 06:21, Linas Vepstas writes:
> After sending the email below, I scanned the guile-devel archives,
> and I see Thomas Morley talking about Lilypond performance.
> The example program he offers up caught my eye: nested deep
> in a loop is this:
>
> (eval-string "'(a b c)")
After sending the email below, I scanned the guile-devel archives,
and I see Thomas Morley talking about Lilypond performance.
The example program he offers up caught my eye: nested deep
in a loop is this:
(eval-string "'(a b c)")
Well -- oh -- ha -- I think this is the same culprit that is one o
So I pulled guile-2.9.1(beta) today, and gave it a spin. Looks
good/great! One bug -- some crazy multithreading bug,
reported as #33641
My use case: guile calling C++ code, which calls guile, which
calls C, ad nauseum. I have some 133 unit tests, of which
maybe 3/4ths tweak guile in some way. All
