From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: epa problem has returned
Date: Mon, 26 May 2014 19:44:49 +0300 [thread overview]
Message-ID: <834n0cjxq6.fsf@gnu.org> (raw)
In-Reply-To: <E1Woar9-0008Ig-Iw@fencepost.gnu.org>
> Date: Sun, 25 May 2014 12:01:03 -0400
> From: Richard Stallman <rms@gnu.org>
> CC: emacs-devel@gnu.org
>
> I stopped it with a signal during that hang
> and it was hung in `read', called from `emacs_read', called
> from `read_process_output', called from `wait_running_process_output'.
> I put a breakpoint on the line in `emacs_read' that calls read,
> and it gets called over and over. `read' returns 0.
>
> Another time it was in pselect called from xg_select called from
> wait_running_process_output.
>
> I tried stepping and saw that it went around the big loop
> in wait_running_process_output (starting at line 4333)
> and did not exit it.
Paul, could this be another manifestation of bug #17561? The symptoms
sound similar to me.
> I can't recall, and can't find, the GDB command to direct
> GDB output to a file.
(gdb) set logging on
This puts all output from GDB on a file named gdb.txt in the directory
where you run GDB.
next prev parent reply other threads:[~2014-05-26 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 10:23 epa problem has returned Richard Stallman
2014-05-21 0:12 ` T.V Raman
2014-05-24 11:32 ` Eli Zaretskii
2014-05-25 0:02 ` raman
2014-05-25 16:01 ` Richard Stallman
2014-05-25 16:23 ` Jorgen Schaefer
2014-05-26 16:44 ` Eli Zaretskii [this message]
2014-05-26 17:10 ` Paul Eggert
2014-05-27 6:11 ` Richard Stallman
2014-05-27 15:28 ` Eli Zaretskii
2014-05-27 15:36 ` Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2014-05-19 9:35 Richard Stallman
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=834n0cjxq6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.