From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Terminal locked when spawning a new tty frame
Date: Wed, 23 Oct 2019 18:48:51 +0100 [thread overview]
Message-ID: <87r233mjy4.fsf@linaro.org> (raw)
In-Reply-To: <875zkftn4u.fsf@igel.home>
Andreas Schwab <schwab@suse.de> 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
next prev parent reply other threads:[~2019-10-23 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 9:56 Terminal locked when spawning a new tty frame Alex Bennée
2019-10-16 10:25 ` Andreas Schwab
2019-10-23 13:31 ` Alex Bennée
2019-10-23 15:38 ` Andreas Schwab
2019-10-23 16:43 ` Alex Bennée
2019-10-23 16:58 ` Andreas Schwab
2019-10-23 17:48 ` Alex Bennée [this message]
2019-11-06 17:17 ` Alex Bennée
2019-10-16 15:12 ` rrandresf
2019-10-16 15:48 ` Eli Zaretskii
2019-10-17 4:47 ` opening an emacs frame on another display (was: Terminal locked when spawning a new tty frame) andrés ramírez
2019-10-17 8:24 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r233mjy4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).