From: William Xu <william.xwl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9264@debbugs.gnu.org
Subject: bug#9264: 24.0.50; (file-error "Creating process pipe" "no error")
Date: Wed, 17 Aug 2011 17:32:26 +0800 [thread overview]
Message-ID: <CACzMC-AuYeuEosaYB_2K2YJbOHPTLr_fTjxKvdBYetoA4U_6zA@mail.gmail.com> (raw)
In-Reply-To: <E1QrSbA-0002nX-LR@fencepost.gnu.org>
2011/8/11 Eli Zaretskii <eliz@gnu.org>:
> We are close. This probably means that we are not closing file
> descriptors somewhere. When these printf's about rc == -1 start to
> appear, can you look at all the elements of the fd_info[] array (there
> are 64 of them), and see which flags are set on most of the elements,
> and whether or not the `cp' member is non-NULL? This information
> might give a clue as to what functionality is stealing the file
> descriptors and not releasing them.
Here is the fd_info array. Most flags are 273, 274 or 0x111, 0x112, namely
FILE_PIPE read and write? And most cp member is NULL, does that imply those are
not properly released ones?
$1 = { {flags = 0, hnd = 0x0, cp = 0x0 },
{flags = 0, hnd = 0x0, cp = 0x0},
{flags = 0, hnd = 0x0, cp = 0x0},
{flags = 1559, hnd = 0x234, cp = 0x13b1200},
{flags = 273, hnd = 0x358, cp = 0x13b1518},
{flags = 273, hnd = 0x0, cp = 0x13b14c0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x13b1468},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x13b1410},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x13b13b8},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x13b1570},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0},
{flags = 273, hnd = 0x0, cp = 0x0},
{flags = 274, hnd = 0x0, cp = 0x0}}
-William
next prev parent reply other threads:[~2011-08-17 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 7:25 bug#9264: 24.0.50; (file-error "Creating process pipe" "no error") William Xu
2011-08-09 8:42 ` Eli Zaretskii
2011-08-11 4:05 ` William Xu
2011-08-11 4:44 ` Eli Zaretskii
2011-08-11 8:25 ` William Xu
2011-08-11 10:34 ` Eli Zaretskii
2011-08-17 9:32 ` William Xu [this message]
2011-09-23 10:55 ` William Xu
2011-09-23 11:04 ` Eli Zaretskii
2011-09-29 16:21 ` Eli Zaretskii
2012-06-05 1:45 ` William Xu
2012-06-05 2:47 ` 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=CACzMC-AuYeuEosaYB_2K2YJbOHPTLr_fTjxKvdBYetoA4U_6zA@mail.gmail.com \
--to=william.xwl@gmail.com \
--cc=9264@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 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.