unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Morgan <sjm@spamcop.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10674@debbugs.gnu.org
Subject: bug#10674: 24.0.92; cmdproxy.exe fork-bomb
Date: Sun, 05 Feb 2012 22:50:10 +0000	[thread overview]
Message-ID: <4F2F07A2.60207@spamcop.net> (raw)
In-Reply-To: <83y5skdwht.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On 03/02/2012 10:47 AM, Eli Zaretskii wrote:
> Please see if ... the second one is the child of the first one and
> the parent of the third one, etc.

This is the case.

> Are you able to run cmdproxy under a debugger and see what is going on
> here?

Not currently.

> If you cannot run cmdproxy under a debugger, please tell:
>
>   . how exactly did you invoke cmdproxy from the command line to get
>     the infinite spawning problem?

Just by executing "cmdproxy.exe" while in "C:\emacs-24.0.92\bin".

>   . do you have other copies of cmdproxy.exe somewhere on your Path?

Nope:

     C:\Users\Simon>where cmdproxy
     INFO: Could not find files for the given pattern(s).

>   . is this Windows 7 box a 32-bit or a 64-bit system?

64-bit.

>   . what is the value of the following Registry key?
>
>      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SafeProcessSearchMode

It doesn't exist.

-- 
The fundamental asymmetry of consciousness means triangulation is the 
only path to understanding.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4783 bytes --]

  reply	other threads:[~2012-02-05 22:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  3:12 bug#10674: 24.0.92; cmdproxy.exe fork-bomb sjm
2012-02-02 17:27 ` Eli Zaretskii
     [not found]   ` <4F2B5793.2010809@spamcop.net>
2012-02-03 10:47     ` Eli Zaretskii
2012-02-05 22:50       ` Simon Morgan [this message]
2012-02-06  3:57         ` Eli Zaretskii
2012-02-06 12:53           ` Simon Morgan
2012-02-06 15:29       ` Simon Morgan
2012-02-06 15:47         ` Juanma Barranquero
2012-02-06 16:57           ` Simon Morgan
2012-02-06 17:50         ` Eli Zaretskii
2012-02-06 18:00           ` Simon Morgan
2012-02-06 21:26             ` Eli Zaretskii
2012-02-06 22:22               ` Simon Morgan
2012-02-07  3:54                 ` Eli Zaretskii
2012-02-07 13:25                   ` Simon Morgan
2012-02-07 17:14                     ` Eli Zaretskii
2012-02-07 18:31                       ` Simon Morgan
2012-02-07 18:45                         ` Eli Zaretskii
2012-02-11 12:08                           ` Eli Zaretskii
2012-02-13 19:25                             ` Simon Morgan
2012-02-13 20:46                               ` Eli Zaretskii
2012-02-19 19:07                                 ` Simon Morgan
2012-02-19 21:16                                   ` Eli Zaretskii
2012-02-24 10:15                                     ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F2F07A2.60207@spamcop.net \
    --to=sjm@spamcop.net \
    --cc=10674@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).