From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Anders Lindgren <andlind@gmail.com>
Cc: 16184@debbugs.gnu.org
Subject: bug#16184: 24.3.50; edebug and eval-when-compiler don't work together
Date: Tue, 24 Dec 2013 09:23:26 +0900 [thread overview]
Message-ID: <b4mwqivp05d.fsf@jpl.org> (raw)
In-Reply-To: <CABr8ebZO6u8AittCrN+GvfJj+n6fj5STCem-_KBjC+V2NyEW9Q@mail.gmail.com>
Anders Lindgren wrote:
> It seems to have solved one problem, but created another. When using
> C-u C-M-x, everything works ok. However, the normal C-M-x command
> issues the error "Too deep - perhaps infinite loop in spec?" When
> enabling debug-on-error, it looks like a very deep call stack (754
> entries). Curiously, it works if I mark the function with the region
> and do "eval-region", it works properly.
Sorry for the delay. But
I'm unable to reproduce such an infloop-like error so far.
Could you show the name or the definition of the function
causing it?
next prev parent reply other threads:[~2013-12-24 0:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 10:58 bug#16184: 24.3.50; edebug and eval-when-compiler don't work together Anders Lindgren
2013-12-20 0:01 ` Katsumi Yamaoka
2013-12-20 6:59 ` Anders Lindgren
2013-12-20 8:28 ` Katsumi Yamaoka
2013-12-20 9:26 ` Anders Lindgren
2013-12-20 9:53 ` Katsumi Yamaoka
2013-12-20 10:30 ` Anders Lindgren
2013-12-20 12:44 ` Katsumi Yamaoka
2013-12-20 13:38 ` Anders Lindgren
2013-12-24 0:23 ` Katsumi Yamaoka [this message]
2013-12-25 22:37 ` Katsumi Yamaoka
2016-10-19 0:06 ` bug#16184: incorrect Edebug spec for eval-and-compile Gemini Lasswell
2016-11-16 1:47 ` bug#16184: confirmed in 25.1 David Bremner
2016-11-16 2:07 ` bug#16184: confirmed on 25.1.1 Benaiah Mischenko
2016-11-18 22:47 ` bug#16184: 24.3.50; edebug and eval-when-compiler don't work together Alan Mackenzie
2016-12-29 9:29 ` Alan Mackenzie
2016-12-30 20:02 ` Anders Lindgren
2016-12-31 16:22 ` Alan Mackenzie
2017-01-01 0:30 ` Anders Lindgren
2017-01-01 8:37 ` Alan Mackenzie
2016-12-30 23:27 ` Gemini Lasswell
2016-12-31 11:18 ` Alan Mackenzie
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mwqivp05d.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=16184@debbugs.gnu.org \
--cc=andlind@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).