[PATCH] Add SIGSEGV processing to send terminating message

[Dan Williams]

On Mon, 2010-02-08 at 11:34 -0800, Dmitry Shmidt wrote:
> Hi,
> 
> In case of segmentation fault it makes sense at least to try to send
> terminating message to network manager.
> Thanks,

Doesn't the client already get notified when the control socket gets
closed because the supplicant dies and drops the other side?

Dan

> Dmitry
> 
> ------------------------------------------------------------------------------------------------------------------------
> From c8e48e9e33e184f45c1c95f5403db8cd4c3e4e1d Mon Sep 17 00:00:00 2001
> From: Dmitry Shmidt <dimitrysh at google.com>
> Date: Mon, 8 Feb 2010 11:29:51 -0800
> Subject: [PATCH] Add SIGSEGV processing to send terminating message
> 
> Signed-off-by: Dmitry Shmidt <dimitrysh at google.com>
> ---
>  src/utils/eloop.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/src/utils/eloop.c b/src/utils/eloop.c
> index ac99989..badab89 100644
> --- a/src/utils/eloop.c
> +++ b/src/utils/eloop.c
> @@ -473,6 +473,8 @@ int
> eloop_register_signal_terminate(eloop_signal_handler handler,
>  	int ret = eloop_register_signal(SIGINT, handler, user_data);
>  	if (ret == 0)
>  		ret = eloop_register_signal(SIGTERM, handler, user_data);
> +	if (ret == 0)
> +		ret = eloop_register_signal(SIGSEGV, handler, user_data);
>  	return ret;
>  }
> 
> _______________________________________________
> HostAP mailing list
> HostAP at lists.shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap