[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Throw an exception when mutating read-only data
From: |
Derek Upham |
Subject: |
Re: [PATCH] Throw an exception when mutating read-only data |
Date: |
Sun, 02 Apr 2017 08:34:26 -0700 |
User-agent: |
mu4e 0.9.17; emacs 25.1.1 |
Andy Wingo <address@hidden> writes:
> * libguile/init.c (scm_i_init_guile): Install the SIGSEGV handler unless
> GUILE_INSTALL_SIGSEGV_HANDLER is 0.
> * libguile/loader.c
> (scm_maybe_throw_exception_for_mutation_of_read_only_data): New public
> function.
> (sigsegv_handler): New helper.
> (scm_install_sigsegv_handler): New public function.
> * libguile/loader.h: Declare new API.
That doesn’t support systems without HAVE_SIGACTION. Do we assume
HAVE_SIGACTION for all systems these days?
The handler setup code is outside of scmsig.c, so there will be conflicts with
the save/restore mechanisms. For example, scm_restore_signals won’t
re-establish that handler.
Derek
--
Derek Upham
address@hidden