GNU bug report logs - #36145
26.2; Unable to "trigger another backtrace"

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 36145 <at> debbugs.gnu.org, Xu Chunyang <mail <at> xuchunyang.me>
Subject: bug#36145: 26.2; Unable to "trigger another backtrace"
Date: Wed, 22 Sep 2021 23:19:52 +0200

Noam Postavsky <npostavs <at> gmail.com> writes:

>> And it's also possible to trigger another backtrace with 'e', if using
>> it from a frame above the debugger's.  I bump into this every so often
>> by accident, and it's quite annoying.  Of course, I'm always in the
>> middle of debugging something else so I forget about it, but I'd like to
>> change it.  Patch attached.

Yes, that's super duper annoying, and it'd be really great to get that
fixed.

>> Subject: [PATCH] Suppress recursive debugger for 'e' command (Bug#36145)
>
> Uh, in my haste to put something down before I forgot about it again, I
> neglected to test this properly; it doesn't actually work.  So I guess
> consider just the doc part of the patch as the proposal, something
> working to follow later.

This was two years ago -- did you get any further with this?

-- 
(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.