From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27920 invoked by alias); 12 May 2014 13:39:28 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 27908 invoked by uid 89); 12 May 2014 13:39:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout20.012.net.il Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 12 May 2014 13:39:24 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0N5G00100R2UEH00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 12 May 2014 16:39:19 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N5G001OGR9JHS00@a-mtaout20.012.net.il>; Mon, 12 May 2014 16:39:19 +0300 (IDT) Date: Mon, 12 May 2014 13:39:00 -0000 From: Eli Zaretskii Subject: Re: GDB-Guile vs. libgc 7.4 marker threads In-reply-to: <87wqdr1l61.fsf_-_@gnu.org> To: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Cc: xdje42@gmail.com, tillmann@selfnet.de, gdb-patches@sourceware.org, wingo@pobox.com Reply-to: Eli Zaretskii Message-id: <83lhu7t8u9.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8BIT References: <83ha54zrry.fsf@gnu.org> <87wqdr1l61.fsf_-_@gnu.org> X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00133.txt.bz2 > From: ludo@gnu.org (Ludovic Courtès) > Cc: Eli Zaretskii , Tillmann Karras , "gdb-patches\@sourceware.org" , Andy Wingo > Date: Mon, 12 May 2014 10:00:22 +0200 > > > https://lists.gnu.org/archive/html/guile-commits/2014-04/msg00051.html > > Yes, but note that this commit is for Guile 2.2. > > That said, although Guile 2.0 builds and runs fine with 7.4 Are you saying that Guile 2.0.x does not suffer from the bug in libgc-7.4.0? > I noticed that GDB-Guile is confused when there are several marker > threads. Thus, we have to set GC_MARKERS=1 when running Guile-GDB > with Guile 2.0 on libgc 7.4. Are you sure this confusion is related to the same libgc issue? Should we talk to libgc developers about that? > Probably the GC_MARKERS hack linked above should be applied to GDB as > well. WDYT? If we are sure this solves the problem, IMO yes. But it would be nice to try to have a new libgc release that is free from this problem, if possible. Also, maybe we should document in the same comment what, if anything, does this restriction mean for GDB-Guile users. Thanks.