From: Sam Steingold <sds@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9945@debbugs.gnu.org
Subject: bug#9945: 24.0.91; crash
Date: Wed, 09 Nov 2011 11:24:06 -0500 [thread overview]
Message-ID: <87ty6dfemx.fsf@gnu.org> (raw)
In-Reply-To: <E1RO687-0005bF-IY@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 09 Nov 2011 06:15:43 -0500")
> * Eli Zaretskii <ryvm@tah.bet> [2011-11-09 06:15:43 -0500]:
>> From: Sam Steingold <sds@gnu.org>
>> On Tue, Nov 8, 2011 at 10:56 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> > Any hope of a reproducible recipe?
>> unlikely.
>
> Can you try at least describing what was being done at the time of the
> crash?
well, I was in a long-running emacs session which all of a sudden became
unresponsive.
ISTR that long ago the crashed emacs's windows became blank and that was
a clear indication of a crash. Now I see the text and menus but emacs
does not respond, and I have to realize that it is crashed and not
busy. Eventually I do realize that and find the gdb screen window, but
by this time I have no idea what I was doing last.
Is there a way to access view-lossage in gdb?
that would be able to jolt my memory...
--
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://dhimmi.com http://palestinefacts.org http://www.memritv.org
http://memri.org http://mideasttruth.com http://iris.org.il
If you know that you know nothing, you know too much.
next prev parent reply other threads:[~2011-11-09 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 18:58 bug#9945: 24.0.91; crash Sam Steingold
2011-11-08 21:21 ` Sam Steingold
2011-11-08 21:28 ` Eli Zaretskii
2011-11-08 21:35 ` Sam Steingold
2011-11-09 3:56 ` Eli Zaretskii
2011-11-09 6:33 ` Sam Steingold
2011-11-09 11:15 ` Eli Zaretskii
2011-11-09 16:24 ` Sam Steingold [this message]
2011-11-09 16:57 ` Eli Zaretskii
2011-11-10 16:35 ` Eli Zaretskii
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=87ty6dfemx.fsf@gnu.org \
--to=sds@gnu.org \
--cc=9945@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.