[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30261: segfault on simultaneous initialization

From: Sheheryar Parvaz
Subject: bug#30261: segfault on simultaneous initialization
Date: Sat, 27 Jan 2018 00:58:06 +0000

Are there any decent workarounds for this? I considered scm_init_guile, however
according to the documentation, it is non-portable. For modules, I have no idea how
I would initialize them.

From: Mark H Weaver <address@hidden>
Sent: January 26, 2018 6:41 PM
To: Sheheryar Parvaz
Cc: address@hidden
Subject: Re: bug#30261: segfault on simultaneous initialization

Sheheryar Parvaz <address@hidden> writes:
> If the initial call to scm_with_guile is on a thread and in the main
> thread at the same time, a segmentation fault occurs.

Yes, this is a known issue.  At present, Guile must be fully initialized
in one thread before it can be safely used from any other thread.
Furthermore, when loading modules, you must ensure that no other thread
attempts to load or use the same module while it's being loaded.  If
possible, please arrange to load all modules that your program will need
before accessing Guile from other threads.

We'd like to fix this at some point, but for various reasons it's a
non-trivial project.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]