From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Crash on startup, "wrong id called on nil"
Date: Sat, 16 Feb 2008 06:27:49 -0800 [thread overview]
Message-ID: <1203172019-sup-1133@south> (raw)
In-Reply-To: <20080207172725.GA9157@gurski.org>
Reformatted excerpts from Michael Gurski's message of 2008-02-07:
> It's been a while since I launched sup, and updating today from
> master, I get a crash on startup:
>
> --- RuntimeError from thread: load threads for thread-index-mode wrong
> id called on nil
Hm, this is a bit tricky. It looks like on of the thread invariants I
maintain is actually a variant.
Although it would be trivial to just guard against this error, it would
be better to find out why it's happening. Would you mind applying the
following patch (just save it to disk and run "git am" on it from your
sup directory), which will emit some debugging output to send-me.txt
when you run Sup and this error occurs. Then you can send me that file
and maybe I can figure out what's going on.
Thanks!
--
William <wmorgan-sup at masanjin.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-add-debugging-code-to-discover-when-Thread-first-ret.patch
Type: application/octet-stream
Size: 1416 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080216/39492fd5/attachment.obj
next prev parent reply other threads:[~2008-02-16 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 17:27 Michael Gurski
2008-02-16 14:27 ` William Morgan [this message]
2008-03-17 16:37 ` William Morgan
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=1203172019-sup-1133@south \
--to=wmorgan-sup@masanjin.net \
/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