From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] 'next' crash: wrong id called on nil (thread.rb:264:in `thread_for')
Date: Wed, 26 Aug 2009 13:26:34 -0700 [thread overview]
Message-ID: <1251318332-sup-4953@yoom.home.cworth.org> (raw)
In-Reply-To: <1251153912-sup-5105@masanjin.net>
Excerpts from William Morgan's message of Mon Aug 24 15:45:37 -0700 2009:
> Reformatted excerpts from Carl Worth's message of 2009-08-20:
> > --- RuntimeError from thread: main
> > wrong id called on nil
>
> I think this should be fixed in recent nexts. Can you confirm?
I don't think I'll be able to, (since I don't have a good recipe for
reproducing the bug). But I'll certainly start running rom newer next
and I'll let you know if I run into any further problems.
Thanks for everything,
-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090826/e9ada9c1/attachment.bin>
prev parent reply other threads:[~2009-08-26 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 2:09 Carl Worth
2009-08-24 22:45 ` William Morgan
2009-08-26 20:26 ` Carl Worth [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=1251318332-sup-4953@yoom.home.cworth.org \
--to=cworth@cworth.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