From: Eli Zaretskii <eliz@gnu.org>
To: sjm@spamcop.net
Cc: 10674-done@debbugs.gnu.org
Subject: bug#10674: 24.0.92; cmdproxy.exe fork-bomb
Date: Fri, 24 Feb 2012 12:15:06 +0200 [thread overview]
Message-ID: <831upktu51.fsf@gnu.org> (raw)
In-Reply-To: <8362f2v801.fsf@gnu.org>
> Date: Sun, 19 Feb 2012 23:16:46 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 10674@debbugs.gnu.org
>
> > Date: Sun, 19 Feb 2012 19:07:57 +0000
> > From: Simon Morgan <sjm@spamcop.net>
> > CC: 10674@debbugs.gnu.org
> >
> > On 13/02/2012 08:46 PM, Eli Zaretskii wrote:
> > > Then please step with a debugger starting at line 555 of cmdproxy.c,
> > > print the values of the variables involved there, and tell me what I
> > > missed.
> >
> > It seems to be working now.
>
> Thanks, that's great news. I will commit those changes in a day or
> two.
Done (revision 107405 on the trunk).
prev parent reply other threads:[~2012-02-24 10:15 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
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 [this message]
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=831upktu51.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10674-done@debbugs.gnu.org \
--cc=sjm@spamcop.net \
/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.