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

Previous Next

Full log

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

From: npostavs <at> users.sourceforge.net
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 13336 <at> debbugs.gnu.org
Subject: Re: bug#13336: 24.3.50;
 `next-frame' should not choose a frame (e.g. *Backtrace*) that did
 not exist when it was invoked
Date: Mon, 30 Jan 2017 22:22:53 -0500

retitle 13336 `next-frame' should not choose the *Backtrace* frame while debugging
quit

Drew Adams <drew.adams <at> oracle.com> writes:
>
> At least in the case of *Backtrace*, which is perhaps a special
> case, it makes no difference whether the frame exists by the
> time `next-frame' is called.  Backtrace acts specially: it does
> not take its own context into account, but instead reflects the
> state of the rest of Emacs.  The debugger should not return the
> *Backtrace* frame.

Ah okay, a special case for *Backtrace* could make sense.  Although I
forsee some tricky edge cases since *Backtrace* is a buffer, not a
frame.

Previous Next

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