bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit


From: Michael Heerdegen
Subject: bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
Date: Tue, 26 Feb 2019 10:56:06 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

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.





reply via email to

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