From: Eli Zaretskii <eliz@gnu.org>
To: stephen_powell@optusnet.com.au
Cc: 13086@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#13086: 24.2.50; Emacs seems to hang at w32proc.c:1126
Date: Thu, 06 Dec 2012 21:48:33 +0200 [thread overview]
Message-ID: <834njzotbi.fsf@gnu.org> (raw)
In-Reply-To: <83624fotw0.fsf@gnu.org>
> > I don't really know what I'm doing, but one odd thing I noticed while
> > playing around with Paul's suggestion to set a breakpoint on
> > delete_process:
> >
> > 1. Set a breakpoint on process.c:808. Print p.pid and do a xbacktrace.
> > 2. Run gnus.
> > 3. Gnus uses imap.el to get mail from my host.
> > 4. Imap.el calls delete-process from imap-close
> >
> > $1 = 1356
> > "delete-process" (0x88bf48)
> > "imap-close" (0x88c248)
> > "mail-source-fetch-imap" (0x88c584)
> >
> > 5. Imap.el calls delete-process to delete the same pid from
> > imap-sentinel
> >
> > $2 = 1356
> > "delete-process" (0x88b928)
> > "imap-sentinel" (0x88bc24)
> > "delete-process" (0x88bf48)
> > "imap-close" (0x88c248)
> > "mail-source-fetch-imap" (0x88c584)
Can you see if the first of these calls to delete-process succeeds to
reap the process? IOW, is it the second call to delete-process that
causes the trouble, e.g., because it asks Emacs to reap a process that
was already reaped?
To see this, put a breakpoint inside get_child_status, or maybe inside
waitpid, and define commands that just display the child PID and
continue, like this:
(gdb) break waitpid
(gdb) commands
> p pid
> continue
> end
(gdb)
Then see how many times waitpid is invoked for the same PID, and
whether it causes assertion violation on the first or the second time
(if there is a second time).
Thanks.
next prev parent reply other threads:[~2012-12-06 19:48 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
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 [this message]
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=834njzotbi.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.