From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 13336@debbugs.gnu.org
Subject: bug#13336: `next-frame' should not choose the *Backtrace* frame while debugging
Date: Mon, 23 Aug 2021 16:37:50 +0200 [thread overview]
Message-ID: <878s0srzup.fsf@gnus.org> (raw)
In-Reply-To: <1776CE98469A44C484752764DD29E2DE@us.oracle.com> (Drew Adams's message of "Wed, 2 Jan 2013 10:13:01 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
> Set `special-display-regexps' or other so that `*Backtrace*' gets
> displayed in its own (special-display) frame.
>
> Evaluate the source code for `next-frame', then
> M-x debug-on-entry next-frame, then C-x o.
>
> When stepping through the debugger, the next frame should never be
> *Backtrace* (unless a *Backtrace* frame existed before invoking `next
> frame'), but it can be. This is a bug IMO.
I don't think so. There's a gazillion things you can do while
edebugging that will make stepping through the code not behave like it
would otherwise (moving frames to different terminals, closing frames,
opening new frames, etc). Adding something special here for *Backtrace*
would just be confusing, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-23 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 18:13 bug#13336: 24.3.50; `next-frame' should not choose a frame (e.g. *Backtrace*) that did not exist when it was invoked Drew Adams
2017-01-30 6:33 ` npostavs
2017-01-30 14:32 ` Drew Adams
2017-01-31 3:22 ` npostavs
2021-08-23 14:37 ` Lars Ingebrigtsen [this message]
2021-08-23 15:20 ` bug#13336: [External] : Re: bug#13336: `next-frame' should not choose the *Backtrace* frame while debugging Drew Adams
2021-08-23 16:06 ` martin rudalics
2021-08-23 17:41 ` Drew Adams
2021-08-24 9:41 ` martin rudalics
2021-08-24 15:49 ` Drew Adams
2021-08-24 17:41 ` martin rudalics
2021-08-24 20:02 ` Drew Adams
2021-08-25 7:48 ` martin rudalics
2021-08-25 15:27 ` Drew Adams
2021-08-25 19:41 ` martin rudalics
2021-08-25 20:23 ` Drew Adams
2021-08-26 7:53 ` martin rudalics
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=878s0srzup.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13336@debbugs.gnu.org \
--cc=drew.adams@oracle.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).