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 736402 - debug logging: Print the GstTask name as well as the thread pointer in the debugs
debug logging: Print the GstTask name as well as the thread pointer in the de...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal enhancement
: 2.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-10 10:21 UTC by Thibault Saunier
Modified: 2018-11-03 12:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thibault Saunier 2014-09-10 10:21:20 UTC 
Currently the debug looks like:

0:00:00.487023893 31989   0x1294590 DEBUG  category ...

where 0x1294590 is the thread as return by g_thread_self. It would be pretty useful to use the name of the GstTask associated when there is one, leading to something like:

0:00:00.487023893 31989   videotestsrc0:src_0x1294590 DEBUG  category ...

What do you think?
Comment 1 Tim-Philipp Müller 2014-09-12 11:45:19 UTC 
I think it would be nice, but I'm not sure if we should put it into the debug log additionally (that's another 18 columns basically), or perhaps we should just put the thread-id <-> name mapping into the debug log with a special identifier for tools like gst-debug-viewer to pick up, and then let gst-debug-viewer show the name instead of the thread ID?

Might also be quite expensive to retrieve the name/task, possibly involving global locks.
Comment 2 Sebastian Dröge (slomo) 2014-09-12 12:46:51 UTC 
That's nice but it would break tools that parse debug logs :)
Comment 3 Thibault Saunier 2014-09-12 12:50:52 UTC 
(In reply to comment #2)
> That's nice but it would break tools that parse debug logs :)

1- I am not sure why, just that the Thread ID field would be longer but I guess the scripts would not care
2- Is our debug logging format supposed to be stable at all?
Comment 4 Sebastian Dröge (slomo) 2014-09-12 13:32:09 UTC 
It's not defined to be stable but people use it like that already since a long time
Comment 5 GStreamer system administrator 2018-11-03 12:22:31 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/74.