[Bug 733187] integrating the tracer branch

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=733187

--- Comment #37 from Stefan Sauer (gstreamer, gtkdoc dev) <ensonic at sonicpulse.de> ---
> - do we have a canonical list somewhere of implemented hooks + arguments
> they will get? If not, that should probably be added to the docs of
> gst_tracing_register_hook() ? Is gsttraceutils.h that list?

I could document all the func pointer typedefs in gsttracerutils. This way I'd
document the params and how the quark string is called. I'd add the doc-blobs
to the GstTracer section. WDYT?

> - core tracers seem to put the thread ID into a guint by casting the result
> of g_thread_self(), don't think that's right

I've been thinking about the options:
a) add G_TYPE_POINTER serialisation to GstValue
   pro: the string would be e.g. thread=(Ptr)0xdeadf00d
   cons: serializing and deserializign a pointer is not meaningful
         (except if the only use is to compare the ids)

b) convert the thread_id to a string in the tracer
   pro: no gstreamer api additons
   cons: we'd serialize it as thread=(String)"0xdeadf00d"

c) generate some 'id' by storing all thread-ids into a array and serializing
the index, the stats-tracer already does something like that for
element/pad-ids. That would become some helper api to be used by all tracers.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.