Re: extra cygwin OutputDebugString spew

2002-04-15 Thread Christopher Faylor
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: cYg 610F5EE0 >>> >>>on my OutputDebugString monitor. >>>Is this really necessary >> >>Yes. >> >>>and can we

Re: extra cygwin OutputDebugString spew

2002-04-15 Thread C. J.
>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: cYg 610F5EE0 >> >>on my OutputDebugString monitor. >>Is this really necessary > >Yes. > >>and can we ditch it for the release cygwin1.dll? > >No. > >cgf Thanks for

Re: extra cygwin OutputDebugString spew

2002-04-11 Thread Christopher Faylor
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: cYg 610F5EE0 > >on my OutputDebugString monitor. >Is this really necessary Yes. >and can we ditch it for the release cygwin1.dll? No. cgf -- Unsubscribe info:

extra cygwin OutputDebugString spew

2002-04-11 Thread C. J.
Every time a cygwin process is started, I get a line like: 3196: cYg 610F5EE0 on my OutputDebugString monitor. Is this really necessary and can we ditch it for the release cygwin1.dll? _ Send and receive Hotmail on your mo