all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Powell <stephen_powell@optusnet.com.au>
To: 12829@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#12829: 24.3.50; emacs_abort () called from w32proc.c:1128
Date: Fri, 09 Nov 2012 18:59:43 +0000	[thread overview]
Message-ID: <509D529F.9090106@optusnet.com.au> (raw)
In-Reply-To: <509AF30F.2020901@optusnet.com.au>

> Did this problem happen again since the original report?  If it does
> happen from time to time, I might ask you to run Emacs under GDB
> with a couple of breakpoints in strategic places, because usually
> when dead_child's handle is NULL, it is too late: the evidence of
> the crime is already forgotten.

Sure. It happens frequently but not always.

> If that GDB session is still active, can you show the entire list in
> deleted_pid_list?  The 'pp' command should be able to display it in
> a human-readable format.

(gdb) pp deleted_pid_list
(5144 5412)





  parent reply	other threads:[~2012-11-09 18:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 23:47 bug#12829: 24.3.50; emacs_abort () called from w32proc.c:1128 Stephen Powell
2012-11-08  3:46 ` Eli Zaretskii
2012-11-08 15:48 ` Stephen Powell
2012-11-09  9:41   ` Eli Zaretskii
2012-11-09 18:59 ` Stephen Powell [this message]
2012-11-09 19:38   ` Eli Zaretskii
2012-11-09 20:16     ` Stephen Powell
2012-11-10  8:27       ` Eli Zaretskii
2012-11-10 14:56         ` Eli Zaretskii
2012-11-10 21:44         ` Paul Eggert
2012-11-11  3:50           ` Eli Zaretskii
2012-11-10 15:45 ` Stephen Powell
2012-11-10 16:09   ` Eli Zaretskii
2012-11-10 18:03 ` Stephen Powell
2012-11-10 18:34   ` Eli Zaretskii
2012-11-17  7:09   ` Eli Zaretskii
2012-11-17 15:35     ` Paul Eggert
2012-11-17 15:40       ` Eli Zaretskii
2012-11-17 16:50         ` Eli Zaretskii
2012-11-17 15:32 ` Stephen Powell

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=509D529F.9090106@optusnet.com.au \
    --to=stephen_powell@optusnet.com.au \
    --cc=12829@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.