This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/2] Demangler crash handler
- From: Gary Benson <gbenson at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Florian Weimer <fw at deneb dot enyo dot de>, Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches at sourceware dot org
- Date: Thu, 15 May 2014 14:27:02 +0100
- Subject: Re: [PATCH 0/2] Demangler crash handler
- Authentication-results: sourceware.org; auth=none
- References: <20140509100656 dot GA4760 at blade dot nx> <201405091120 dot s49BKO1f010622 at glazunov dot sibelius dot xs4all dot nl> <87fvkhjqvs dot fsf at mid dot deneb dot enyo dot de> <53737737 dot 2030901 at redhat dot com>
Pedro Alves wrote:
> ...stealing a signal handler always has multi-threading
> considerations. E.g., gdb Python code could well spawn a thread
> that happens to call something that wants its own SIGSEGV handler...
> Signal handlers are per-process, not per-thread.
I had not considered this. Do you know of any specific libraries
that do it? The only times I've seen SIGSEGV handlers in the wild
have been in VMs and other language-level stuff.
Thanks,
Gary
--
http://gbenson.net/