Re: Mainloop debugging tool idea

[Alexander Larsson <alexl redhat com>]

On mån, 2012-11-19 at 00:55 +0100, Bastien Nocera wrote:
> Heya,
> 
> I had some problems with gnome-shell's responsiveness on particularly
> dodgy hardware, and was wondering whether the shell was actually
> blocking at any point.
> 
> Came the idea of using of watchdog thread, based on the mainloop, which
> would check for how long the mainloop was running a particular
> iteration, and have to dump a backtrace if the main loop was blocking on
> a particular task for more than X amount of time.
> 
> Does anyone have code like that available? If not, where would one plug
> that code into the main loop code in gmain.c?
> 
> This would make testing problems like the ones split off from:
> https://bugzilla.gnome.org/show_bug.cgi?id=687362
> much easier.

Another thing I've long wanted was to be able to list all the
outstanding sources from gdb. Its a total pain to debug async apps right
now, because getting a backtrace just gives you the mainloop. Now that 
sources can get names (g_source_set_name) we should also be able to get
a list of all outstanding sources, kinda like an async backtrace.