GDB-Guile vs. libgc 7.4 marker threads

Andy Wingo wingo@pobox.com
Thu May 15 07:46:00 GMT 2014


On Mon 12 May 2014 15:39, Eli Zaretskii <eliz@gnu.org> writes:

>> > https://lists.gnu.org/archive/html/guile-commits/2014-04/msg00051.html
>> 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.

I have asked for a new libgc release, but I have not gotten a response.
I will ask again.

Setting GC_MARKERS=1 is not visible to the user.  There is no change in
functionality.  Using multiple mark threads is purely an optimization.
So I don't think it needs to be documented.

Regards,

Andy
-- 
http://wingolog.org/



More information about the Gdb-patches mailing list