From: Andy Wingo <wingo@pobox.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ludo@gnu.org (Ludovic Courtès),
xdje42@gmail.com, tillmann@selfnet.de,
gdb-patches@sourceware.org
Subject: Re: GDB-Guile vs. libgc 7.4 marker threads
Date: Thu, 15 May 2014 07:46:00 -0000 [thread overview]
Message-ID: <87ha4reb7n.fsf@pobox.com> (raw)
In-Reply-To: <83lhu7t8u9.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 May 2014 16:39:10 +0300")
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/
prev parent reply other threads:[~2014-05-15 7:46 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
2014-05-13 15:53 ` Ludovic Courtès
2014-05-15 7:46 ` Andy Wingo [this message]
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=87ha4reb7n.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=tillmann@selfnet.de \
--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