[gstreamer-bugs] [Bug 347794] New: Do not reset SIGSEGV handler when --gst-disable-segtrap is active
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Mon Jul 17 08:12:55 PDT 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=347794
GStreamer | gstreamer (core) | Ver: 0.10.8
Summary: Do not reset SIGSEGV handler when --gst-disable-segtrap
is active
Product: GStreamer
Version: 0.10.8
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gstreamer (core)
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: michal.benes at xeris.cz
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
I am writing an application that has custom SIGSEGV handler. Unfortunately the
function _gst_plugin_fault_handler_restore resets the handler to SIG_DFL, even
if _gst_disable_segtrap == TRUE. Note that my pipe is builded automatically and
therefore new plugins can be loaded anytime during the stream processing.
I propose that _gst_plugin_fault_handler_restore does nothing in the case that
_gst_plugin_fault_handler_setup did not set the signal handler. Simple patch
attached. More complex patch could use _gst_plugin_fault_handler_is_setup, but
I am not sure what was the developers intention with this flag.
It would be also nice to have API for setting _gst_disable_segtrap = TRUE from
the application.
Thanks Michal
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Gstreamer-bugs
mailing list