Hi all,
I've come to the conclusion that this problem is unsolvable and I will
abandon the idea of an at-exit-hook. The most serious potential consequence
of running it in really_cleanup_for_exit(), which is indirectly invoked
through atexit(), is that the resources to clean up or the Guile librar
On Thu, 7 Nov 2024 17:10:45 +0100
Maxime Devos wrote:
> On Thu, 7 Nov 2024 12:23:08 +0100
> >Maxime Devos wrote:
> >> ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> >> handlers (*). Since the hook runs Scheme code, it could do a lot of
> >> AC-unsafe things, resulting in p
On Thu, 7 Nov 2024 17:10:45 +0100
Maxime Devos wrote:
> On Thu, 7 Nov 2024 12:23:08 +0100
> >Maxime Devos wrote:
> >> ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> >> handlers (*). Since the hook runs Scheme code, it could do a lot of
> >> AC-unsafe things, resulting in p
On Thu, 7 Nov 2024 12:23:08 +0100
>Maxime Devos wrote:
>> ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
>> handlers (*). Since the hook runs Scheme code, it could do a lot of
>> AC-unsafe things, resulting in problems.
>>
>> (*) glibc documentation says ‘exit’ is AC-unsafe,
OK, so people have brought up two issues:
1. It is for various reasons not recommended to call atexit() from a
dynamically linked library (which Guile already does before my suggested
change, n.b.).
2. It is not async signal safe.
A suggested remedy would then be:
Instead of calling the at-exit
On Thu, 7 Nov 2024 12:09:25 +
Mailer wrote:
> On Thu, 7 Nov 2024 12:23:08 +0100
> Maxime Devos wrote:
> > ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> > handlers (*). Since the hook runs Scheme code, it could do a lot of
> > AC-unsafe things, resulting in problems.
>
How about using sigprocmask to disable async signals temporarily?
On Thu, Nov 7, 2024 at 8:23 PM Maxime Devos wrote:
> ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> handlers (*). Since the hook runs Scheme code, it could do a lot of
> AC-unsafe things, resulting in probl
On Thu, 7 Nov 2024 12:23:08 +0100
Maxime Devos wrote:
> ‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal
> handlers (*). Since the hook runs Scheme code, it could do a lot of
> AC-unsafe things, resulting in problems.
>
> (*) glibc documentation says ‘exit’ is AC-unsafe, but th
‘atexit’ functions are run at ‘exit’. ‘exit’ can be run from signal handlers
(*). Since the hook runs Scheme code, it could do a lot of AC-unsafe things,
resulting in problems.
(*) glibc documentation says ‘exit’ is AC-unsafe, but this is unsupported by
POSIX AFAICT. OTOH the same applies to ev
Hi,
I think it would be good to have an at-exit-hook which is run atexit(). The
motivation is that Guile can provide bindings for libraries which may want
to clean up resources at exit. If the at-exit-hook exists, this would then
be one way to make sure that the linked in library can do this at ex
10 matches
Mail list logo
