After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157127 - Cleanup of issues reported by sparse
Cleanup of issues reported by sparse
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.8.8
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-02 11:35 UTC by Kjartan Maraas
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch to fix warnings reported by sparse (14.12 KB, patch)
2004-11-02 11:36 UTC, Kjartan Maraas
none Details | Review

Description Kjartan Maraas 2004-11-02 11:35:39 UTC
This patch removes some warnings reported by sparse. Mostly NULL vs FALSE vs 0
and some ANSIfication of function declarations.
Comment 1 Kjartan Maraas 2004-11-02 11:36:10 UTC
Created attachment 33341 [details] [review]
patch to fix warnings reported by sparse
Comment 2 Ronald Bultje 2004-11-02 11:41:56 UTC
 /* static variables for segfault handling of plugin loading */
 static char *_gst_plugin_fault_handler_filename = NULL;
-extern gboolean *_gst_disable_segtrap;  /* see gst.c */
+extern gboolean _gst_disable_segtrap;  /* see gst.c */
 
 #ifndef HAVE_WIN32
-static gboolean *_gst_plugin_fault_handler_is_setup = FALSE;
+static gboolean _gst_plugin_fault_handler_is_setup = FALSE;
 #endif

those two scare me. The rest all looks fine, they're cosmetic and don't change
anything.
Comment 3 Wim Taymans 2004-11-02 15:02:24 UTC
patch commited to CVS
Comment 4 Kjartan Maraas 2004-11-02 15:52:10 UTC
Did you look at _gst_disable_segtrap in gst.c? It's declared as
gboolean _gst_disable_segtrap = FALSE; there so why is it a pointer to a
gboolean here? Doesn't look right in the _gst_plugin_fault_handler_is_setup case
either...
Comment 5 Ronald Bultje 2004-11-02 17:51:00 UTC
Ah, OK. Yes, Wim committed it correctly. Let's close this.