From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, 34535@debbugs.gnu.org
Subject: bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
Date: Tue, 26 Feb 2019 10:56:06 +0100 [thread overview]
Message-ID: <87ef7uvpop.fsf@web.de> (raw)
In-Reply-To: <83va17narr.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 25 Feb 2019 17:33:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> This isn't informative enough, I need a C-level backtrace plus a full
> Lisp backtrace. Please next time attach a debugger when this happens,
> source Emacs's src/.gdbinit, and type "thread apply all bt" at GDB
> prompt.
Ok, I'll do that.
> Also, I don't think I understand how you got the above Lisp backtrace:
> by default SIGUSR2 does nothing. Do you have some handler for it? if
> so, what does it do?
No, I only use the default behavior:
-- User Option: debug-on-event
If you set ‘debug-on-event’ to a special event (*note Special
Events::), Emacs will try to enter the debugger as soon as it
receives this event, bypassing ‘special-event-map’. At present,
the only supported values correspond to the signals ‘SIGUSR1’ and
‘SIGUSR2’ (this is the default). This can be helpful when
‘inhibit-quit’ is set and Emacs is not otherwise responding.
(Why do you think SIGUSR2 would do nothing?)
Michael.
next prev parent reply other threads:[~2019-02-26 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:29 bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit Michael Heerdegen
2019-02-22 16:08 ` Eli Zaretskii
2019-02-22 20:09 ` Eli Zaretskii
2019-02-22 20:25 ` Eli Zaretskii
2019-02-23 4:27 ` Michael Heerdegen
2019-02-23 8:21 ` Eli Zaretskii
2019-02-23 15:13 ` Stefan Monnier
2019-02-23 16:54 ` Eli Zaretskii
2019-02-24 7:16 ` Michael Heerdegen
2019-02-24 16:06 ` Eli Zaretskii
2019-02-25 7:09 ` Michael Heerdegen
2019-02-25 15:33 ` Eli Zaretskii
2019-02-26 9:56 ` Michael Heerdegen [this message]
2019-02-26 15:26 ` Eli Zaretskii
2019-02-26 17:27 ` Michael Heerdegen
2019-02-26 18:27 ` Eli Zaretskii
2019-03-01 10:21 ` 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=87ef7uvpop.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34535@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.