Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: kevinr@free-dissociation.com (Kevin Riggle)
Subject: [sup-talk] Exceptions around saving drafts
Date: Sun, 26 Oct 2008 18:07:23 -0400	[thread overview]
Message-ID: <1225058548-sup-3222@black-opal> (raw)

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
-- 
Kevin Riggle (kevinr at free-dissociation.com) 
http://free-dissociation.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20081026/20fa0a0e/attachment.txt>


             reply	other threads:[~2008-10-26 22:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 22:07 Kevin Riggle [this message]
2008-10-27 12:12 ` Nicolas Pouillard
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=1225058548-sup-3222@black-opal \
    --to=kevinr@free-dissociation.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