From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 13611-done@debbugs.gnu.org, Mike Gran <spk121@yahoo.com>
Subject: bug#13611: SEGV during SMOB GC
Date: Wed, 13 Mar 2013 13:42:38 +0100 [thread overview]
Message-ID: <87obenh3nl.fsf@pobox.com> (raw)
In-Reply-To: <87txov6ok7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 01 Mar 2013 18:02:32 +0100")
On Fri 01 Mar 2013 18:02, ludo@gnu.org (Ludovic Courtès) writes:
> AFAICS, commit 01b69e7 fixes the problem for me. I tested with your
> test-smob-mark.c program, both with a 7.2ish and 7.3ish libgc.
>
> Can you confirm that it works for you, and commit your test case with
> the changes as discussed on the list?
Changes committed, closing bug. Thanks, all!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-03-13 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 20:51 bug#13611: SEGV during SMOB GC Mike Gran
2013-02-05 10:07 ` Ludovic Courtès
2013-02-05 16:29 ` Mike Gran
2013-02-05 16:41 ` Ludovic Courtès
2013-02-05 17:04 ` Mike Gran
2013-02-05 21:13 ` Ludovic Courtès
2013-02-06 4:56 ` Mike Gran
2013-03-01 17:02 ` Ludovic Courtès
2013-03-13 12:42 ` 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
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=87obenh3nl.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13611-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=spk121@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).