From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Crash while scrolling
Date: Sat, 26 Sep 2009 07:31:56 -0700 [thread overview]
Message-ID: <1253975267-sup-8308@masanjin.net> (raw)
In-Reply-To: <20090916172340.GA20566@ben-laptop>
Sorry it's taken me so long to get back to this.
Reformatted excerpts from Ben Gamari's message of 2009-09-16:
> Thread#join: deadlock 0x7f592eec4d78 - mutual join(0x7f592f01d6e8)
> /opt/exp/sup/lib/sup/message.rb:240:in `select'
> /opt/exp/sup/lib/sup/buffer.rb:35:in `nonblocking_getch'
> /usr/bin/sup:213
>
> However, at this point during debugging I happened to pipe stderr to a
> file and accidentally found that most of the backtrace was actually
> being hidden by curses. Examining the full output on stderr reveals,
>
> /usr/bin/sup:213(eval):3:in `synchronize': Thread#join: deadlock
> 0x7f4d5da565c0 - mutual join(0x7f4d5daf8be0) (ThreadError)
> from (eval):3:in `raw_header'
> from /opt/exp/sup/lib/sup/imap.rb:98:in `load_header'
I definitely am not sure why there's a deadlock happening, but I am
guessing, based on the line numbers in that first exception, that it's
being triggered by an underlying problem with the source. If you run
sup with -n, does that change anything? (Or produce a better exception?)
> Anyways, this is the current status of things on my machine. William, do
> you have any ideas what might cause such a backtrace. At this point
> classes have started and I really have no more time to devote to
> getting sup working. If there isn't a fairly simple solution here I guess
> I'll just need to stick with mutt (ugh). Anyways, thanks for your work.
Well, there's a workaround, which is to switch over to an offlineimap
setup where your Gmail is mirrored locally and Sup reads the mirror
(which is what you want anyways if you're serious about using Sup with
an IMAP client). I don't know what's causing the deadlock, but I will
try and reproduce it on my end.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-26 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 16:58 Ben Gamari
2009-09-12 16:35 ` William Morgan
2009-09-13 15:02 ` Ben Gamari
2009-09-16 17:23 ` Ben Gamari
2009-09-26 14:31 ` William Morgan [this message]
2009-09-28 18:10 ` Ben Gamari
2009-10-01 13:43 ` William Morgan
2009-10-01 17:44 ` Ben Gamari
2009-10-01 18:31 ` William Morgan
2009-10-01 19:01 ` Ben Gamari
2009-10-11 20:31 ` William Morgan
2009-10-01 18:41 ` [sup-talk] Writing time-sensitive portions of sup in C Carl Worth
2009-09-30 21:21 ` [sup-talk] Crash while scrolling William Morgan
2009-10-04 19:59 ` Guillaume Quintard
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=1253975267-sup-8308@masanjin.net \
--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