[Gstreamer-bugs] [Bug 116618] Changed - desynchronized clock?

[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=116618

Changed by rbultje at ronald.bitfreak.net.

--- shadow/116618	Thu Jul  3 05:55:58 2003
+++ shadow/116618.tmp.28591	Thu Jul  3 07:15:43 2003
@@ -1,13 +1,13 @@
 Bug#: 116618
 Product: GStreamer
 Version: 0.6.2
 OS: FreeBSD
 OS Details: 5.1
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: normal
 Priority: Normal
 Component: gstreamer (core)
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
 ReportedBy: laurent at datarescue.be               
 QAContact: gstreamer-maint at bugzilla.gnome.org
@@ -50,6 +50,22 @@
 Clock info: speed 1.000000, active yes, time 1762407704
 Clock info: speed 1.000000, active yes, time -1522543592
 Clock info: speed 1.000000, active yes, time -512522592
 Clock info: speed 1.000000, active yes, time 497485408
 Clock info: speed 1.000000, active yes, time 1507503408
 
+
+------- Additional Comments From rbultje at ronald.bitfreak.net  2003-07-03 07:15 -------
+It's an integer overflow. Use guint64. ;).
+
+The maximum value of a gint is 2^31, that being rightly around 2,1M.
+After that, it flips back to its minimum value, that being around
+-2,1M. From there, it increases again and goes its cycle around again.
+
+Since we measure time in nanoseconds, one second is already
+approximately 2^30. Two seconds can barely be hold in one gint, and
+three seconds is far too much. I don't think the clock is broken, your
+test case simply can't hold it. To fix this, use %ulld (on 32bit
+platforms) or %uld (on 64bit platforms), this can also be typed as
+G_GUINT64_FORMAT (a glib macro for this), and don't cast the return
+value to an integer in g_print(). Then, it should work. If it doesn't
+please reopen. For now, I'll mark this as a non-bug.