GNU bug report logs - #13336
`next-frame' should not choose the *Backtrace* frame while debugging

Previous Next

Full log

Message #23 received at 13336 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 13336 <at> debbugs.gnu.org
Subject: Re: bug#13336: `next-frame' should not choose the *Backtrace* frame
 while debugging
Date: Mon, 23 Aug 2021 16:37:50 +0200

"Drew Adams" <drew.adams <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.