From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27036@debbugs.gnu.org
Subject: bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!!
Date: Thu, 25 May 2017 15:43:14 +0300 [thread overview]
Message-ID: <a200fbb7-7b57-d849-78b1-a3dc952d5b75@yandex.ru> (raw)
In-Reply-To: <83zie2krcg.fsf@gnu.org>
On 5/24/17 10:05 PM, Eli Zaretskii wrote:
> If you can reproduce this at will, run under GDB, put a breakpoint at
> the line which emits the message, and when it breaks, produce a
> backtrace. I'd expect the offending code to be evident from that,
> especially if you also run "xbacktrace" to see the Lisp backtrace.
Here it is:
Thread 1 "emacs" hit Breakpoint 3, wait_reading_process_output
(time_limit=0, nsecs=0, read_kbd=read_kbd@entry=0,
do_display=do_display@entry=false,
wait_for_cell=wait_for_cell@entry=XIL(0),
wait_proc=wait_proc@entry=0x1399c30 <bss_sbrk_buffer+7942096>,
just_wait_proc=0) at process.c:5015
5015 message1 ("Blocking call to accept-process-output with quit
inhibited!!");
(gdb) xbacktrace
"accept-process-output" (0xffffb980)
"inferior-octave-send-list-and-digest" (0xffffbc78)
"octave-eldoc-function-signatures" (0xffffbf68)
"octave-eldoc-function" (0xffffc410)
"apply" (0xffffc408)
0x13fef90 PVEC_COMPILED
"eldoc-print-current-symbol-info" (0xffffc950)
0xa3dc38 PVEC_COMPILED
"apply" (0xffffcd58)
"timer-event-handler" (0xffffd0a8)
Any ideas?
eldoc-print-current-symbol-info uses with-demoted-errors, which expands
into a condition-case, but does that inhibit quitting somehow?
And inferior-octave-send-list-and-digest uses unwind-protect.
next prev parent reply other threads:[~2017-05-25 12:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 12:20 bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!! Francesco Potortì
2017-05-24 12:24 ` Dmitry Gutov
2017-05-24 18:01 ` Eli Zaretskii
2017-05-24 18:17 ` Dmitry Gutov
2017-05-24 19:05 ` Eli Zaretskii
2017-05-25 12:43 ` Dmitry Gutov [this message]
2017-05-25 12:51 ` Noam Postavsky
2017-05-25 16:14 ` Eli Zaretskii
2017-05-26 1:02 ` Dmitry Gutov
2017-05-26 6:07 ` Eli Zaretskii
2017-05-26 0:38 ` Dmitry Gutov
[not found] ` <handler.27036.B.1495542030639.ack@debbugs.gnu.org>
2017-05-24 11:21 ` bug#27036: Acknowledgement (25.1; Blocking call to accept-process-output with quit inhibited!!) Francesco Potortì
2017-05-24 14:27 ` Francesco Potortì
2017-05-24 17:57 ` Eli Zaretskii
2017-05-25 15:58 ` Francesco Potortì
2017-05-26 0:41 ` Dmitry Gutov
2017-05-26 13:17 ` Francesco Potortì
2017-05-27 0:22 ` Dmitry Gutov
2017-05-30 7:46 ` Francesco Potortì
2017-05-30 22:39 ` Dmitry Gutov
2017-09-28 21:06 ` Dmitry Gutov
2017-09-29 7:03 ` Francesco Potortì
2022-04-23 15:24 ` bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!! Lars Ingebrigtsen
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=a200fbb7-7b57-d849-78b1-a3dc952d5b75@yandex.ru \
--to=dgutov@yandex.ru \
--cc=27036@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).