Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 15 Apr 2002 15:34:08 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: extra cygwin OutputDebugString spew Message-ID: <20020415193408.GB15842@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Mon, Apr 15, 2002 at 12:20:40PM -0700, C. J. wrote: >>On Thu, Apr 11, 2002 at 04:38:09PM -0700, C. J. wrote: >>Every time a cygwin process is started, I get a line like: >>>3196: cYgFFFFFFFF 610F5EE0 >>> >>>on my OutputDebugString monitor. >>>Is this really necessary >> >>Yes. >> >>>and can we ditch it for the release cygwin1.dll? >> >>No. > >Thanks for the explanation. You didn't ask for an explanation: http://www.tuxedo.org/~esr/faqs/smart-questions.html If you want insight into low-level details about cygwin, the source code is the place to find it. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/