From: "Ludovic Courtès" <INVALID.NOREPLY@gnu.org>
To: ludo@gnu.org, b3timmons@speedymail.org, 9833@debbugs.gnu.org
Subject: bug#9833: [bug #34616] Segfault when building against debug version of bdw-gc (patch offered)
Date: Sat, 22 Oct 2011 11:34:50 +0000 [thread overview]
Message-ID: <20111022-113450.sv15145.88050@savannah.gnu.org> (raw)
In-Reply-To: <20111022-034858.sv66629.51424@savannah.gnu.org>
Update of bug #34616 (project guile):
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Thanks for the report! I committed a slightly different version in commit
80fc43f2cf12c7a21a0533cc84e91059ef9d8170.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34616>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2011-10-22 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 3:48 bug#9829: [bug #34616] Segfault when building against debug version of bdw-gc (patch offered) Bake Timmons
2011-10-22 11:34 ` Ludovic Courtès [this message]
2011-10-22 15:58 ` bug#9833: " Ludovic Courtès
2013-03-10 20:12 ` bug#9829: " 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111022-113450.sv15145.88050@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=9833@debbugs.gnu.org \
--cc=b3timmons@speedymail.org \
--cc=ludo@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).