From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Peter Brett <peter@peter-b.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Help needed debugging segfault with Guile 1.8.7
Date: Thu, 11 Nov 2010 13:37:05 +0100 [thread overview]
Message-ID: <871v6sqbny.fsf@ambire.localdomain> (raw)
In-Reply-To: <we1m1v6snnd2.fsf@ssclt001.eps.surrey.ac.uk> (Peter Brett's message of "Thu, 11 Nov 2010 10:52:41 +0000")
() Peter Brett <peter@peter-b.co.uk>
() Thu, 11 Nov 2010 10:52:41 +0000
stupid logic error in some weak ref management code
Could you please describe this error?
next prev parent reply other threads:[~2010-11-11 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:43 Help needed debugging segfault with Guile 1.8.7 Peter TB Brett
2010-11-10 21:35 ` Peter TB Brett
2010-11-11 10:52 ` Peter Brett
2010-11-11 12:37 ` Thien-Thi Nguyen [this message]
2010-11-11 14:22 ` Peter Brett
2010-11-28 11:38 ` Neil Jerram
2010-11-28 17:21 ` Linas Vepstas
2010-11-30 19:56 ` Peter TB Brett
2010-12-01 19:48 ` Andy Wingo
2010-11-30 19:43 ` Peter TB Brett
2010-12-01 13:46 ` Ludovic Courtès
2010-12-03 7:52 ` Peter TB Brett
2010-11-11 8:22 ` rixed
2010-11-11 8:33 ` Neil Jerram
2010-11-11 13:30 ` Ludovic Courtès
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=871v6sqbny.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=peter@peter-b.co.uk \
/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).