From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: process_send_string blocks?
Date: Sun, 07 Sep 2014 18:44:51 +0300 [thread overview]
Message-ID: <83egvncu4s.fsf@gnu.org> (raw)
In-Reply-To: <85tx4jn8mz.fsf@stephe-leake.org>
> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Date: Sun, 07 Sep 2014 03:21:24 -0500
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stephen Leake <stephen_leake@stephe-leake.org>
> >>
> >> I have a reliable reproducer, which I can easily simplify.
> >
> > Please do simplify it and post it. Having a way of debugging this by
> > several people will definitely make the process more efficient, and
> > probably produce a higher quality solution.
>
> Posted bug#18420. Unfortunately, when I simplify the external process
> code, the hang goes away; I don't understand why, yet.
Too bad it cannot be simplified.
> In general, nothing the external process does should hang Emacs, short
> of crashing the OS.
Not sure what you are saying here. How can a crashing OS hang Emacs?
> > Btw, do you see the problem in "emacs -Q"?
>
> Yes, but only with the full external process code and full Ada mode
> code.
So you are saying that sending text to the subprocess somehow depends
on the major mode? That'd be surprising.
> I did manage to attach a debugger to the running processes; that's a
> first for me :). It was useful for the Ada code (compiled with debug
> info), but not for the Emacs process; it says the stack is corrupted.
See my response to the bug report: most probably, you are running an
optimized binary, where backtraces blatantly lie.
next prev parent reply other threads:[~2014-09-07 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 8:09 process_send_string blocks? Stephen Leake
2014-09-06 8:28 ` Jorgen Schaefer
2014-09-06 9:34 ` Eli Zaretskii
2014-09-06 13:11 ` Stephen Leake
2014-09-06 13:28 ` Eli Zaretskii
2014-09-07 8:21 ` Stephen Leake
2014-09-07 15:44 ` Eli Zaretskii [this message]
2014-09-07 20:32 ` Stephen Leake
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=83egvncu4s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.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).