From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: dcl441-bugs@yahoo.com
Cc: 2966@debbugs.gnu.org
Subject: bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger
Date: Fri, 16 Sep 2011 22:24:32 +0200 [thread overview]
Message-ID: <m3k498utfj.fsf@stories.gnus.org> (raw)
In-Reply-To: <663334.62553.qm@web53204.mail.re2.yahoo.com> (Daniel Clemente's message of "Sat, 11 Apr 2009 19:01:47 -0700 (PDT)")
Daniel Clemente <dcl441-bugs@yahoo.com> writes:
> Eval anything with (debug) on it, like:
>
> (let* ((x 3) (y 1))
> (debug)
> (dotimes (a x) (setq y (* y x)))
> y
> )
>
> When the debugger appears, press e to evaluate some symbol. You can
> type x RET to see the value of x. But now try a symbol which doesn't
> exist, for instance z. You get:
>
> Debugger entered--Lisp error: (void-variable z)
> eval(z)
> eval-expression(z)
> debugger-eval-expression(z)
> call-interactively(debugger-eval-expression nil nil)
> recursive-edit()
>
> And at this point, your debugger session is (apparently) lost and
> you can't continue debugging your program: e.g. "c" doesn't work and
> it only says (error "Cannot return from the debugger in an error")
This was marked as notabug wontfix, but it's apparently been fixed
anyway. :-)
You now get a further bug and your environment isn't lost:
Debugger entered--Lisp error: (void-variable z)
eval(z nil)
eval-expression(z nil)
call-interactively(eval-expression nil nil)
recursive-edit()
debug()
eval((debug) nil)
eval-expression((debug) nil)
call-interactively(eval-expression nil nil)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-09-16 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 2:01 bug#2966: 23.0.92; A typing error in debugger-eval-expression stops the debugger Daniel Clemente
2011-09-16 20:24 ` Lars Magne Ingebrigtsen [this message]
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=m3k498utfj.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=2966@debbugs.gnu.org \
--cc=dcl441-bugs@yahoo.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 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.