From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 15931@debbugs.gnu.org
Subject: bug#15931: 24.3.50; emacs_backtrace.txt
Date: Wed, 20 Nov 2013 10:22:25 -0800 (PST) [thread overview]
Message-ID: <bcd4832d-3d52-45d4-a3ef-e6d03d58edb4@default> (raw)
In-Reply-To: <<8361rney2t.fsf@gnu.org>>
> > The last time, at least, was using C-g in the minibuffer.
> >
> > This is the command that C-g is bound to there, but it ends by
> > doing just `abort-recursive-edit'. I suspect that is where the
> > crash occurs, since I'm not aware of changes that would affect
> > the rest of it.
>
> Thanks, but I cannot try this because this function calls a few
> others that you didn't show.
>
> Could you please prepare a self-contained recipe that could be used
> to reproduce the problem? Also, does one need to configure the session
> in some special way for this to happen, e.g., open more than one
> frame etc.? Or should this work from "emacs -Q"?
I do not have a recipe to reproduce the crash. If the extra info
I gave, besides the backtrace, does not help, please ignore it.
I was hoping that mentioning `abort-recursive-edit' might help.
next parent reply other threads:[~2013-11-20 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<e65bac53-a880-470d-82b3-3d09a4f0f306@default>
[not found] ` <<6148cdba-2dcc-4cce-94e4-422da323dc89@default>
[not found] ` <<8361rney2t.fsf@gnu.org>
2013-11-20 18:22 ` Drew Adams [this message]
2013-11-20 18:28 ` bug#15931: 24.3.50; emacs_backtrace.txt Eli Zaretskii
[not found] <<bcd4832d-3d52-45d4-a3ef-e6d03d58edb4@default>
[not found] ` <<831u2bexly.fsf@gnu.org>
2013-11-20 18:30 ` Drew Adams
2013-11-19 23:20 Drew Adams
2013-11-20 0:50 ` Drew Adams
2013-11-20 18:18 ` Eli Zaretskii
2013-11-20 18:26 ` 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=bcd4832d-3d52-45d4-a3ef-e6d03d58edb4@default \
--to=drew.adams@oracle.com \
--cc=15931@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.