From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Exceptions around saving drafts
Date: Mon, 27 Oct 2008 13:12:39 +0100 [thread overview]
Message-ID: <1225109441-sup-9989@ausone.inria.fr> (raw)
In-Reply-To: <1225058548-sup-3222@black-opal>
I also had this problem and never took time to debug it or report a bug.
Generally sup-sync fix it. Sometimes also working on a draft can duplicate
it and trying to remove the duplicate leads to this problem. Last time
I directly ran a console and removed it from the index.
Excerpts from Kevin Riggle's message of Sun Oct 26 23:07:23 +0100 2008:
> Working with a draft message today got me lots of exceptions, usually
> when I saved the draft and went back to my inbox. (These all took the
> same form, so I've only attached one of them.) Running sup-sync didn't
> help. Attempting to /delete/ a draft (open the message, hit 'e' on the
> draft, quit my editor, close the buffer in Sup, hit 'y' for discard) got
> me a segfault in Ruby (the stock Ubuntu package thereof):
>
> ./lib/sup/draft.rb:38: [BUG] Segmentation fault ruby 1.8.6 (2007-09-24) [x86_64-linux]
> Aborted
>
> FYI.
>
> - Kevin
> --- EOFError from thread: main
> End-of-File Error occured at <except.c>:93 in xraise
> Error occured in compound_io.c:137 - cmpdi_read_i
> Tried to read past end of file. File length is <1> and tried to read to <30056>
>
> ./lib/sup/draft.rb:38:in `default'
> ./lib/sup/draft.rb:38:in `[]'
> ./lib/sup/draft.rb:38:in `discard'
> ./lib/sup/util.rb:499:in `send'
> ./lib/sup/util.rb:499:in `method_missing'
> ./lib/sup/modes/resume-mode.rb:43:in `save_as_draft'
> ./lib/sup/mode.rb:49:in `send'
> ./lib/sup/mode.rb:49:in `handle_input'
> ./lib/sup/buffer.rb:240:in `handle_input'
> bin/sup:189
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2008-10-27 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 22:07 Kevin Riggle
2008-10-27 12:12 ` Nicolas Pouillard [this message]
2008-10-28 2:21 ` William Morgan
2008-10-29 9:09 ` Nicolas Pouillard
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=1225109441-sup-9989@ausone.inria.fr \
--to=nicolas.pouillard@gmail.com \
/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