[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug #2110] bug in threading implementation using guile-1.6.1

From: Stan Pinte
Subject: Re: [Bug #2110] bug in threading implementation using guile-1.6.1
Date: Fri, 10 Jan 2003 15:23:20 +0100
User-agent: Opera M2 7.0 build 2349

On Fri, 10 Jan 2003 15:13:35 +0100, Mikael Djurfeldt <address@hidden> wrote:

address@hidden writes:

=================== BUG #2110: LATEST MODIFICATIONS ==================

Changes by: Stan Pinte <address@hidden>
Date: 2003-Jan-10 13:38 (GMT)

------------------ Additional Follow-up Comments ------------------------

This only seems to happen when I make two calls two (gtk-main), indirectly.

-> one via the (gtk-ensure-handler) call
-> one afterwards, via the (gtk-main) call.

Well, this is not a correct usage pattern.  (gtk-ensure-handler)
spawns a gtk handler which handles all events of the application.
That is, it is an *alternative* to (gtk-main).

If your intention with calling gtk-main is to wait for the application
to quit, I suggest that you wait on a condition variable instead.
Then make sure that it is signalled when the application quits.
(But maybe someone else more versed in guile-gtk have a better

If I do what you describe in an interactive guile session, I get a lot
of glib warning messages which are properly informative:

g_main_iterate(): main loop already active in another thread

It would of course be nicer not to get stuck in a loop but just get
*one* error message...

that is exactly the same as I get. thanks for helping.

Best regards,
Mikael Djurfeldt

Stan Pinte

reply via email to

[Prev in Thread] Current Thread [Next in Thread]