From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Mikael Djurfeldt Newsgroups: gmane.lisp.guile.bugs,gmane.lisp.guile.user Subject: Re: [Bug #2110] bug in threading implementation using guile-1.6.1 Date: Fri, 10 Jan 2003 15:13:35 +0100 Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Message-ID: References: Reply-To: djurfeldt@nada.kth.se NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1042208181 14962 80.91.224.249 (10 Jan 2003 14:16:21 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 10 Jan 2003 14:16:21 +0000 (UTC) Cc: djurfeldt@nada.kth.se Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18WzxM-0003tB-00 for ; Fri, 10 Jan 2003 15:16:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18WzwM-0000zR-06 for guile-bugs@m.gmane.org; Fri, 10 Jan 2003 09:15:18 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18Wzvk-0000FE-00 for bug-guile@gnu.org; Fri, 10 Jan 2003 09:14:40 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18Wzvf-0000Cg-00 for bug-guile@gnu.org; Fri, 10 Jan 2003 09:14:36 -0500 Original-Received: from kvast.blakulla.net ([213.212.20.77]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18Wzuk-0007zn-00; Fri, 10 Jan 2003 09:13:38 -0500 Original-Received: from barbara.blakulla.net ([213.212.21.238] helo=linnaeus) by kvast.blakulla.net with esmtp (Exim 3.36 #1 (Debian)) id 18Wzui-00053g-00; Fri, 10 Jan 2003 15:13:36 +0100 Original-Received: from mdj by linnaeus with local (Exim 3.36 #1 (Debian)) id 18Wzuh-00022I-00; Fri, 10 Jan 2003 15:13:35 +0100 Original-To: stan.pinte@wanadoo.be, bug-guile@gnu.org, guile-user@gnu.org In-Reply-To: (nobody@savannah.gnu.org's message of "Fri, 10 Jan 2003 08:38:41 -0500") User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GUILE, GNU's Ubiquitous Extension Language List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.bugs:621 gmane.lisp.guile.user:1523 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.bugs:621 nobody@savannah.gnu.org writes: > =================== BUG #2110: LATEST MODIFICATIONS ================== > http://savannah.gnu.org/bugs/?func=detailbug&bug_id=2110&group_id=39 > > Changes by: Stan Pinte > 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 suggestion.) 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... Best regards, Mikael Djurfeldt _______________________________________________ Bug-guile mailing list Bug-guile@gnu.org http://mail.gnu.org/mailman/listinfo/bug-guile