Re: GDB-Guile vs. libgc 7.4 marker threads

Eli Zaretskii
2014-05-12T13:39:28Z

> 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.