[Gstreamer-bugs] [Bug 127815] Changed - gst-register sigsegs 100% of the time.

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=127815

Changed by thomas at apestaart.org.

--- shadow/127815	Fri Dec 12 12:59:03 2003
+++ shadow/127815.tmp.4982	Fri Feb  6 10:42:06 2004
@@ -6,13 +6,13 @@
 Status: NEEDINFO   
 Resolution: 
 Severity: major
 Priority: Normal
 Component: gstreamer (core)
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
-ReportedBy: jnelson at jamponi.net               
+ReportedBy: jnelson-gnome at jamponi.net               
 QAContact: gstreamer-maint at bugzilla.gnome.org
 TargetMilestone: HEAD
 URL: 
 Summary: gst-register sigsegs 100% of the time.
 
 Distribution: Unknown
@@ -195,28 +195,28 @@
         rclass = (GstRegistryClass *) 0x805b21c
 #10 0x08048fce in main (argc=1, argv=0xbffffba4) at gst-register.c:85
         registry = (GstRegistry *) 0x80503e8
         registries = (GList *) 0x8050638
         path_spill = (GList *) 0x0
 
-------- Additional Comments From jnelson at jamponi.net  2003-11-26 10:51 -------
+------- Additional Comments From jnelson-gnome at jamponi.net  2003-11-26 10:51 -------
 *** Bug 127986 has been marked as a duplicate of this bug. ***
 
-------- Additional Comments From jnelson at jamponi.net  2003-11-26 15:52 -------
+------- Additional Comments From jnelson-gnome at jamponi.net  2003-11-26 15:52 -------
 More data.
 This was compiled with the latest gcc (3.3.2) and propolice (3.3-5).
 When -fstack-protector-all is used, that's what triggers the sigseg.
 I'm not sure /why/, but there is clearly a buffer overrun or a bug in
 propolice.
 
 
 ------- Additional Comments From rbultje at ronald.bitfreak.net  2003-11-26 16:24 -------
 Then I assume you want to add a bug there instead of here? This
 doesn't sound like a GStreamer bug then...
 
-------- Additional Comments From jnelson at jamponi.net  2003-11-26 16:28 -------
+------- Additional Comments From jnelson-gnome at jamponi.net  2003-11-26 16:28 -------
 Well, no, it's still a buffer overrun.
 
 The difference is that propolice catches it an aborts gstreamer,
 rather than allowing it to continue after what it believes at this
 point is a buffer overrun.
 
@@ -226,6 +226,10 @@
 I have never seen backtraces look like that.
 two threads, same backtrace with same pointers, the second one having
 more info ?
 
 what dist are you on, and what sort of non-standard stuff did you do
 to the build to get the first bt ?
+
+------- Additional Comments From thomas at apestaart.org  2004-02-06 10:42 -------
+ping, please comment
+