From: sup-talk@gurski.org (Michael Gurski)
Subject: [sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on nil"
Date: Tue, 11 Mar 2008 20:51:46 -0400 [thread overview]
Message-ID: <1205282947-sup-6038@ln> (raw)
In-Reply-To: <521619824.20080311020608@rice.edu>
Excerpts from Christopher Warrington's message of Tue Mar 11 03:06:08 -0400 2008:
>
> Alexandra Walford @ 2008-3-10 11:45:43 PM
> "[sup-talk] [Crash] "thread_by_subject: true" leads to "wrong id called on
> nil"" <mid:1205210652-sup-1364 at amethyst>
>
> > 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.
>
> Sorry! :-)
>
> The first message was created with sup. The second with git's
> send-email command. I've not looked at them closely, but the messages
> may be malformed.
>
Interestingly, the crashes I was seeing with the same error seem to
have disappeared now that I've disabled thread_by_subject as well.
Once I get past the huge amount of backlog in mail that I have (who'd
have thought getting married would eat into my copious free time?),
I'll rerun sup and try to get the debugging output from the patch that
I applied to create a sendme.txt when this happens.
Mike
--
Michael A. Gurski (opt. [first].)[last]@pobox.com http://www.pobox.com/~[last]
1024R/39B5BADD PGP: 34 93 A9 94 B1 59 48 B7 17 57 1E 4E 62 56 45 70
1024D/1166213E GPG: 628F 37A4 62AF 1475 45DB AD81 ADC9 E606 1166 213E
4096R/C0B4F04B GPG: 5B3E 75D7 43CF CF34 4042 7788 1DCE B5EE C0B4 F04B
Views expressed by the host do not reflect the staff, management or sponsors.
next prev parent reply other threads:[~2008-03-12 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 4:45 Alexandra Walford
2008-03-11 7:06 ` Christopher Warrington
2008-03-12 0:51 ` Michael Gurski [this message]
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=1205282947-sup-6038@ln \
--to=sup-talk@gurski.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