From: nyc4bos@aol.com
To: martin rudalics <rudalics@gmx.at>
Cc: 10034@debbugs.gnu.org
Subject: bug#10034: 24.0.91; max-specpdl-size error
Date: Sun, 13 Nov 2011 18:01:42 -0500 [thread overview]
Message-ID: <84obwfpqy1.fsf@aol.com> (raw)
In-Reply-To: <4EBFA0B7.20400@gmx.at> (martin rudalics's message of "Sun, 13 Nov 2011 11:49:27 +0100")
martin rudalics <rudalics@gmx.at> writes:
>> Eventually, I would get into a state where I couldn't do much, seeing
>> messages like:
>>
>> window-min-size-1: Variable binding depth exceeds max-specpdl-size
>>
>> I then could only kill Emacs.
>
> Do you mean that Emacs looped and C-g didn't quit? If you can see a
> message like the above, C-g usually works.
C-g worked. However, other things that I did resulted in
"Variable binding depth exceeds max-specpdl-size" messages.
>
>> In GNU Emacs 24.0.91.1 (i386-mingw-nt5.1.2600)
>> of 2011-11-07 on MARVIN
>
> IIUC this is with a build made _before_ Chong's `window-total-size'
> change, so the latter can't be the culprit.
I was using the "emacs-20111107-r106319-bin-i386.zip" Windows version.
>
> I can't propose much about this at the moment. If this happens again
> and you can get back to the command loop via C-g, try to open a new
> frame via C-x 5 2 and look at the last lines of the *Messages* buffer.
> If for some reason you can't make a new frame, try C-x 1 instead.
The specific error message that I listed above:
window-min-size-1: Variable binding depth exceeds max-specpdl-size
occurred when I tried to `C-SPC C-h M-w' the *Message* buffer.
When I was geting different "max-specpdl-size" errors with almost
everything I subsequently did, I started up a new Emacs instance in
order to file a bug report.
I then tried to copy the *Message* buffer from the original Emacs
instance that was having this problem into the new Emacs instance in
order to provide information for the bug report.
I could `C-x b' (switch-to-buffer) to the *Message* buffer and a few
other things but most things resulted in different "max-specpdl-size"
warning messages.
(BTW, I noticed that after sending a bug report and successfully
sending with `C-c C-c', the Bug Report Help buffer created when
invoking `(report-emacs-bug)' at least from the menu-bar, remains
visible as another (split) window. Is that intentional?)
next prev parent reply other threads:[~2011-11-13 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 4:46 bug#10034: 24.0.91; max-specpdl-size error nyc4bos
2011-11-13 10:49 ` martin rudalics
2011-11-13 23:01 ` nyc4bos [this message]
2011-11-14 8:54 ` martin rudalics
2011-11-14 14:38 ` Drew Adams
2011-11-16 2:59 ` nyc4bos
2011-11-14 1:24 ` nyc4bos
2011-11-14 8:54 ` martin rudalics
2011-11-16 3:14 ` nyc4bos
2011-11-16 3:43 ` nyc4bos
2011-11-16 4:01 ` Eli Zaretskii
2011-11-19 5:32 ` nyc4bos
2011-11-19 8:12 ` Eli Zaretskii
2011-12-09 23:48 ` bug#7658: 24.0.50; emacsclient not raising frame nyc4bos
2011-11-14 14:08 ` bug#10034: 24.0.91; max-specpdl-size error Stefan Monnier
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=84obwfpqy1.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=10034@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.