Ryujinx-GtkSharp/gtk/gui-thread-check
2012-11-04 00:32:09 +00:00
..
profiler gui-thread-check: Remove bogus Makefile.in 2012-11-04 00:27:00 +00:00
AUTHORS Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
ChangeLog Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
COPYING Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
gui-thread-check.sln Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
INSTALL Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
Makefile.am Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
NEWS Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00
README Moved gui-thread-check subfolder inside gtk subfolder. 2012-11-03 23:06:02 +00:00

The gui-thread-check profile module
===================================

This profiler module can be used to check if a GTK# application is trying to
invoke gtk or gdk methods from a thread which is not the main GUI thread.

To use it, build and install the module, and then run your application with
the command:

  mono --profile=gui-thread-check yourapp.exe

If the profiler is properly installed, you'll see an output like this:

*** Running with gui-thread-check ***
*** GUI THREAD INITIALIZED: 2861676352

While the application is running, if the profiler detects a non-gui thread
invoking gtk methods, it will print a warning message together with a
stack trace. For example:

*** GTK CALL NOT IN GUI THREAD: Widget.gtk_widget_get_parent
   Widget.get_Parent
   SourceEditorWidget.SetLastActiveEditor
   SourceEditorWidget.get_TextEditor
   SourceEditorWidget.get_Document
   SourceEditorWidget.HandleParseInformationUpdaterWorkerThreadDoWork
   BackgroundWorker.OnDoWork
   BackgroundWorker.ProcessWorker