GNU bug report logs - #21587
Mac: Segfault when unloading shared object linked to libguile

Previous Next

Full log

Message #16 received at 21587-done <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: Wilhelm Schuster <wilhelm <at> wilhelm.re>
Cc: 21587-done <at> debbugs.gnu.org
Subject: Re: bug#21587: Mac: Segfault when unloading shared object linked to
 libguile
Date: Tue, 28 Feb 2017 15:29:31 +0100

Closing as not-a-bug given discussion below.  Please reply if you have
additional comments/etc.  Thanks.

Andy

On Fri 24 Jun 2016 14:32, Andy Wingo <wingo <at> pobox.com> writes:

> On Tue 29 Sep 2015 20:21, Wilhelm Schuster <wilhelm <at> wilhelm.re> writes:
>
>> The basic run down: When I try to unload (using dlclose() ) a shared
>> object that is linked to libguile after calling scm_init_guile() OR
>> scm_with_guile(), a Segfault is triggered.
>
> Hummmmmmmmmmmm!  Well, so this is quite tricky.  Loading Guile loads
> Guile which might start threads (some helper threads behind the scenes
> for finalization (see section on scm_set_automatic_finalization_enabled
> in tha manual), perhaps a thread to listen for signals, and then the
> garbage collector that we use (libgc) might start parallel marking
> threads (though you can control that parameter too).
>
> Guile doesn't really provide an interface to allow it to shut down
> cleanly and I don't know if it can.  (I guess it could.)  However it
> would take quite some amount of work and I don't see us doing it any
> time soon.  In any case simply trying to dlclose() is never likely to
> work, as you aren't synchronizing with Guile itself.
>
> Sorry for the bad news!
>
> Andy

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.