[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20734: 25.0.50; "Args out of range" with help-window-select t
From: |
Nicolas Richard |
Subject: |
bug#20734: 25.0.50; "Args out of range" with help-window-select t |
Date: |
Fri, 05 Jun 2015 11:33:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> We can however get a gdb backtrace (I put a breakpoint in Fsignal, but
>> it breaks more often than needed, so I say "continue" a few times in
>> order to get the following) :
>
> You can put a break point in maybe_call_debugger, which tends to work
> better in this sense.
Thanks. Would the following make sense in etc/DEBUG ?
-`Fsignal' is a very useful place to put a breakpoint in.
-All Lisp errors go through there.
+`Fsignal' is a very useful place to put a breakpoint in. All Lisp
+errors go through there. If you are only interested in errors that
+would fire the debugger, breaking at `maybe_call_debugger' is useful.
--
Nico.
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Nicolas Richard, 2015/06/04
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Stefan Monnier, 2015/06/04
- bug#20734: 25.0.50; "Args out of range" with help-window-select t,
Nicolas Richard <=
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Eli Zaretskii, 2015/06/05
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Nicolas Richard, 2015/06/05
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Eli Zaretskii, 2015/06/05
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Nicolas Richard, 2015/06/05
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Eli Zaretskii, 2015/06/05
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Nicolas Richard, 2015/06/06
- bug#20734: 25.0.50; "Args out of range" with help-window-select t, Eli Zaretskii, 2015/06/06