all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 13086@debbugs.gnu.org, stephen_powell@optusnet.com.au
Subject: bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126
Date: Thu, 06 Dec 2012 20:41:30 +0200	[thread overview]
Message-ID: <83d2ynowf9.fsf@gnu.org> (raw)
In-Reply-To: <50C04ADB.3080002@cs.ucla.edu>

> Date: Wed, 05 Dec 2012 23:35:55 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: stephen_powell@optusnet.com.au, 13086@debbugs.gnu.org
> 
> I found a race condition in delete-process that
> looks like it might be relevant, and installed
> a patch as trunk bzr 111122.  Could you please
> give that a try?

I also found some potential problem in w32proc.c, and fixed that in
revision 111132 on the trunk.  Stephen, please try the latest code and
see if the problem persists.

> If it doesn't fix the problem,
> it might help to see whether the problem is related
> to delete-process.  E.g., you might plant a breakpoint
> on Fdelete_process and see what sort of calls are
> being made to it.  Another possibility is to put
> a breakpoint on waitpid, to see what arguments are
> being passed to it and what it returns -- maybe
> you can insert some code to print out that info
> to a file.

Yes, if Emacs still loops where it did in your original report, please
tell what does waitpid set errno to, and through which 'return' line
does it return to its caller.

I find DebPrint useful for this -- is fast and causes GDB to display a
string when you run Emacs under GDB.  You will see examples of its
usage in w32proc.c and elsewhere.

Thanks.





  reply	other threads:[~2012-12-06 18:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  7:22 bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126 Stephen Powell
2012-12-05 16:42 ` Eli Zaretskii
2012-12-05 19:28 ` Stephen Powell
2012-12-05 21:25   ` Eli Zaretskii
2012-12-06  2:04     ` Paul Eggert
2012-12-06  3:51       ` Eli Zaretskii
2012-12-06  5:07         ` Paul Eggert
2012-12-06 18:28           ` Eli Zaretskii
2012-12-06 20:18             ` Paul Eggert
2012-12-06 20:25               ` Eli Zaretskii
2012-12-06 20:36                 ` Paul Eggert
2012-12-06 20:39                   ` Eli Zaretskii
2012-12-06 20:48                     ` Eli Zaretskii
2012-12-06 21:36                       ` Paul Eggert
2012-12-07  6:22                         ` Eli Zaretskii
2012-12-07 17:54                           ` Paul Eggert
2012-12-07 18:57                             ` Eli Zaretskii
2012-12-06 20:57                     ` Paul Eggert
2012-12-07  6:46                       ` Eli Zaretskii
2012-12-07 16:48                         ` Ken Brown
2012-12-07 17:43                           ` Paul Eggert
2012-12-06  7:35         ` Paul Eggert
2012-12-06 18:41           ` Eli Zaretskii [this message]
2012-12-06  5:07 ` Stephen Powell
2012-12-06 19:10 ` Stephen Powell
2012-12-06 19:36   ` Eli Zaretskii
2012-12-06 19:48     ` Eli Zaretskii
2012-12-06 20:17 ` Stephen Powell
2012-12-06 20:36   ` Eli Zaretskii
2012-12-06 22:51 ` Stephen Powell
2012-12-07  6:43   ` Eli Zaretskii
2012-12-07  0:10 ` Stephen Powell
2012-12-07  6:44   ` Eli Zaretskii
2012-12-21 11:56   ` Eli Zaretskii
2012-12-23 17:12     ` Eli Zaretskii
2013-01-22 13:38   ` 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=83d2ynowf9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13086@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=stephen_powell@optusnet.com.au \
    /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.