GNOME Bugzilla – Bug 793268
debug-viewer: crash when loading model in timeline
Last modified: 2018-02-08 15:30:18 UTC
Traceback (most recent call last):
+ Trace 238382
main ()
GstDebugViewer.run ()
paths=Paths)
options["main"](options)
app.run()
Common.Main.MainLoopWrapper(Gtk.main, Gtk.main_quit).run()
self.__update_params()
model.get(tree_iter, model.COL_TIME, model.COL_THREAD))
values.append(self.get_value(treeiter, col))
I tracked the issue down to the "thread" column model handling. If the thread id isn't converted to an integer, there's no crash: diff --git a/debug-viewer/GstDebugViewer/Data.py b/debug-viewer/GstDebugViewer/Data.py index 567c018..090b2c0 100644 --- a/debug-viewer/GstDebugViewer/Data.py +++ b/debug-viewer/GstDebugViewer/Data.py @@ -392,7 +392,7 @@ class LogLine (list): # PID. line[1] = int(line[1]) # Thread. - line[2] = int(line[2], 16) + # line[2] = int(line[2], 16) # Level (this is handled in LineCache). line[3] = 0 # Line. I'm really not a GTK+ expert but this might be a bug elsewhere, perhaps in python-gobject. I use version 3.26.1-2 on Debian Testing FWIW.
Presumably fixed by: Author: Olivier Crête <olivier.crete@collabora.com> Date: Thu Feb 8 08:20:55 2018 -0700 debug-viewer; Store thread as long instead of int On 64-bit platforms, the thread id can be over 2^32 so use a long to handle it. If not, please re-open, thanks!