all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:31:23 +0100	[thread overview]
Message-ID: <CAHDbmO2qrHEfu1Rpv9pr4KJDi=aLHULmTd-5tx_f-Co3v3vTXg@mail.gmail.com> (raw)
In-Reply-To: <mvmeezddm2p.fsf@suse.de>

It's reproduced for me but so far nothing obvious sticks out:

(gdb) p kboard_stack
$1 = (struct kboard_stack *) 0x0
(gdb) p single_kboard
$2 = true
(gdb) c
Continuing.

On Wed, 16 Oct 2019 at 11:25, Andreas Schwab <schwab@suse.de> wrote:
>
> On Okt 16 2019, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> > So any ideas on how I can debug this next time it occurs?
>
> I'd suggest to attach with a debugger and inspect kboard_stack and
> single_kboard.
>
> Andreas.
>
> --
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."



-- 
Alex Bennée
KVM/QEMU Hacker for Linaro



  reply	other threads:[~2019-10-23 13:31 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHDbmO2qrHEfu1Rpv9pr4KJDi=aLHULmTd-5tx_f-Co3v3vTXg@mail.gmail.com' \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.