[Bug awt/25375] awt / swt clash

[greenrd at gcc dot gnu dot org]

------- Comment #2 from greenrd at gcc dot gnu dot org  2006-04-30 10:03 -------
I see two issues which could be causing this:

1. While the AWT peer synchronises access to gdk using gdk_threads_enter and
gdk_threads_leave, SWT doesn't use those particular functions at all.

2. The API doc for g_thread_init says "g_thread_init() must not be called
directly or indirectly as a callback from GLib. Also no mutexes may be
currently locked, while calling g_thread_init()." It also says "g_thread_init()
might only be called once. On the second call it will abort with an error." (By
abort, does it mean abort() or just return?) I am not sure that the current
code guarantees these rules will be followed! And there may be rules for other
functions that are broken, too.

However, GTK-mozilla does embed successfully in SWT, despite the lack of calls 
to gdk_threads_enter that I identified in issue 1. I will investigate how that
works.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25375