Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: xdje42@gmail.com, tillmann@selfnet.de,
	gdb-patches@sourceware.org, wingo@pobox.com
Subject: Re: GDB-Guile vs. libgc 7.4 marker threads
Date: Mon, 12 May 2014 13:39:00 -0000	[thread overview]
Message-ID: <83lhu7t8u9.fsf@gnu.org> (raw)
In-Reply-To: <87wqdr1l61.fsf_-_@gnu.org>

> From: ludo@gnu.org (Ludovic Courtès)
> Cc: Eli Zaretskii <eliz@gnu.org>,  Tillmann Karras <tillmann@selfnet.de>,  "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>, Andy Wingo <wingo@pobox.com>
> 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.


  reply	other threads:[~2014-05-12 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 16:58 [PATCH v2 00/36] Guile extension language for GDB Tillmann Karras
2014-04-27 22:15 ` Doug Evans
2014-05-04 19:59   ` Tillmann Karras
2014-05-05  6:03     ` Eli Zaretskii
2014-05-12  3:25       ` Doug Evans
2014-05-12  8:00         ` GDB-Guile vs. libgc 7.4 marker threads Ludovic Courtès
2014-05-12 13:39           ` Eli Zaretskii [this message]
2014-05-13 15:53             ` Ludovic Courtès
2014-05-15  7:46             ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lhu7t8u9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ludo@gnu.org \
    --cc=tillmann@selfnet.de \
    --cc=wingo@pobox.com \
    --cc=xdje42@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox