From: kevinr@mit.edu (Kevin Riggle)
Subject: [sup-talk] Crash report: Draft message weirdness
Date: Wed, 07 May 2008 19:11:14 -0400 [thread overview]
Message-ID: <1210201416-sup-3219@black-opal> (raw)
See attached -- I believe these crashes are all related. It seems like
there's some corruption, likely in the draft message store.
I opened up a draft message I had saved on a thread of them, and when I
was finished editing it, I tried to send it, and sup crashed. For some
reason when I restarted there were two draft copies of that message on
the thread. I tried to remove one of the drafts by editing it, closing
the editor, then killing the buffer, and saying 'y' when it asked me to
discard, and Sup crashed. I restarted and tried to archive some
messages, including, I think, the one with the drafts saved on it, and
when I hit $ to save the changes, Sup crashed.
- Kevin
--
Kevin Riggle (kevinr at mit.edu)
http://free-dissociation.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: deletion-exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080507/a649a9b3/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: discard-draft-exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080507/a649a9b3/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: save-changes-exception-log.txt
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080507/a649a9b3/attachment-0002.txt>
next reply other threads:[~2008-05-07 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 23:11 Kevin Riggle [this message]
2008-05-07 23:13 ` Kevin Riggle
2008-05-19 23:21 ` 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=1210201416-sup-3219@black-opal \
--to=kevinr@mit.edu \
/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