[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Terminal locked when spawning a new tty frame

From: Alex Bennée
Subject: Re: Terminal locked when spawning a new tty frame
Date: Wed, 23 Oct 2019 18:48:51 +0100
User-agent: mu4e 1.3.5; emacs 27.0.50

Andreas Schwab <address@hidden> writes:

> On Okt 23 2019, Alex Bennée wrote:
>> #13 0x000055ed55d1f5f6 in recursive_edit_1 () at keyboard.c:714
>> #14 0x000055ed55d1f915 in Frecursive_edit () at keyboard.c:786
>> #15 0x000055ed55d8e2a3 in Ffuncall (nargs=1, args=args@entry=0x7ffd0aca1ca8) 
>> at lisp.h:2109
>> #16 0x000055ed55dc1d51 in exec_byte_code (bytestr=<optimized out>, 
>> vector=<optimized out>, maxdepth=<optimized out>, args_template=<optimized 
>> out>, nargs=<optimized out>, args=<optimized out>) at bytecode.c:633
>> #17 0x000055ed55d8e1ff in Ffuncall (nargs=3, args=0x7ffd0aca2060) at 
>> eval.c:2808
>> #18 0x000055ed55d8e532 in Fapply (nargs=nargs@entry=2, 
>> args=args@entry=0x7ffd0aca20f0) at eval.c:2424
>> #19 0x000055ed55d8e66c in apply1 (fn=<optimized out>, 
>> arg=arg@entry=0x55ed5d981de3) at lisp.h:1399
>> #20 0x000055ed55d8e858 in call_debugger (arg=0x55ed5d981de3) at eval.c:339
>> #21 0x000055ed55d8ef01 in maybe_call_debugger (data=0x55ed5d1a9ec3, 
>> sig=0xe520, conditions=0x7f26ae4ed72b) at lisp.h:1032
>> #22 0x000055ed55d8ef01 in signal_or_quit (error_symbol=0xe520, 
>> data=0x55ed5d1a9ec3, keyboard_quit=<optimized out>) at eval.c:1666
>> #23 0x000055ed55c44214 in Fsignal (error_symbol=<optimized out>, 
>> error_symbol@entry=0xe520, data=<optimized out>) at eval.c:1568
> So you have a frame inside the debugger, probably because debug-on-error
> is non-nil.

I'll check next time. I might of knocked it on by mistake. The other
Andrés mentioned one workaround was killing an errant *Backtrace* but I
must admit I didn't check if the debugger was active during the failure.

> Andreas.

Alex Bennée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]