From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: sshd fork failure
Date: Sat, 13 Oct 2012 21:05:00 -0000 [thread overview]
Message-ID: <5079D77A.8040908@gmail.com> (raw)
In-Reply-To: <20121013192612.GB10736@ednor.casa.cgf.cx>
On 10/13/2012 9:26 PM, Christopher Faylor wrote:
>
> No. This has nothing to do with cygwin1.dbg. The address 61137DC8 is
> in the middle of an instruction.
>
> cgf
>
after a second rebaseall and a full updatedb to look for any
other cygwin1.dll, now sshd is working as expected.
It does not make sense.....
waiting to see 1.7.17
Thanks
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-10-13 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 21:59 marco atzeri
2012-10-13 15:39 ` Christopher Faylor
2012-10-13 16:10 ` marco atzeri
2012-10-13 16:54 ` Christopher Faylor
2012-10-13 18:21 ` marco atzeri
2012-10-13 18:25 ` Christopher Faylor
2012-10-13 19:22 ` marco atzeri
2012-10-13 19:26 ` Christopher Faylor
2012-10-13 21:05 ` marco atzeri [this message]
2012-10-13 21:17 ` Gregory M. Turner
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=5079D77A.8040908@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).