From: alexandra@walford.id.au (Alexandra Walford)
Subject: [sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on nil"
Date: Tue, 11 Mar 2008 14:45:43 +1000 [thread overview]
Message-ID: <1205210652-sup-1364@amethyst> (raw)
Hi all,
I am getting frequent sup crashes with "wrong id called on nil" (using the
latest git master), when thread_by_subject is true.
The crash generally happens when the thread index is being built as a result of
a search, or when opening the inbox (which is really just another sort of
search).
I have managed to narrow down one particular crash to two messages sent to the
sup-talk list. If I set up a new maildir containing only those two messages
and a new sup config, accepting all sup-config defaults and changing
thread_by_subject to true, then I can reproduce the crash reliably. The second
message References: the first message, although the subjects are dissimilar.
I have attached the two messages, a transcript of my test case session
(including backtrace), and sup-exception-log.txt. I am not yet familiar enough
with sup or ruby to offer a decent patch; my current fix just hides any thread
which will cause a crash, on line 208 of lib/sup/modes/thread-index-mode.rb in
git master, which is a hopeless workaround really.
Thanks,
Alexandra
--
alexandra at walford.id.au
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: message1.txt
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20080311/3d1a1cb1/attachment.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: message2.txt
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20080311/3d1a1cb1/attachment-0001.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sup-exception-log.txt
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20080311/3d1a1cb1/attachment-0002.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sup-test-case.txt
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20080311/3d1a1cb1/attachment-0003.txt
next reply other threads:[~2008-03-11 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:45 Alexandra Walford [this message]
2008-03-11 7:06 ` Christopher Warrington
2008-03-12 0:51 ` Michael Gurski
2008-03-14 18:51 ` William Morgan
2008-03-14 22:28 ` Alexandra Walford
2008-03-17 16:41 ` William Morgan
2008-03-18 12:35 ` Alexandra Walford
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=1205210652-sup-1364@amethyst \
--to=alexandra@walford.id.au \
/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