Re: Bug? wcsxfrm causing memory corruption

2017-05-20 Thread Duncan Roe
On Wed, May 10, 2017 at 11:30:46AM +0200, Erik Bray wrote: > Greetings-- > > In the process of fixing the Python test suite on Cygwin I ran across > one test that was consistently causing segfaults later on, not > directly local to that test. The test involves wcsxfrm so that's > where I focused m

Re: crash on environment name beginning with non-ASCII char (64 bit)

2017-05-20 Thread Steven Penny
On Sat, 20 May 2017 19:07:41, Steven Penny wrote: Crap, I was confused by your wording. *I can* repro this if the variable *name* begins with non-ASCII. Sadly, this appears to affect Dash as well, so it goes all the way down to the Cygwin DLL, as you said. -- Problem reports: http://cyg

Re: crash on environment name beginning with non-ASCII char (64 bit)

2017-05-20 Thread Steven Penny
On Sat, 20 May 2017 19:04:31, Steven Penny wrote: in which case I would ask you to see if the problem persists with Dash, or if it is exclusive to Bash. However I am not able to repro your issue. I tried it in pristine Windows 7 virtual machine with: Crap, I was confused by your wording. *I can

Re: crash on environment name beginning with non-ASCII char (64 bit)

2017-05-20 Thread Steven Penny
On Sat, 20 May 2017 22:04:21, Thomas Wolff wrote: If an environment variable is set in the Windows environment that has a name beginning with a non-ASCII character (e.g. "äx", value "test"), initialising the 64-bit cygwin dll fails: *** fatal error - internal error reading the windows environmen

crash on environment name beginning with non-ASCII char (64 bit)

2017-05-20 Thread Thomas Wolff
If an environment variable is set in the Windows environment that has a name beginning with a non-ASCII character (e.g. "äx", value "test"), initialising the 64-bit cygwin dll fails: *** fatal error - internal error reading the windows environment - too many environment variables? No problem wit

Re: 5 seconds to update link info?

2017-05-20 Thread Richard H Lee
On 20/05/2017 01:39, Andrey Repin wrote: I've tried to disable NetBIOS over TCP/IP on client for all adapters active, but nothing has changed. You could always try using Wireshark to get more insight as to what is causing the delay. -- Problem reports: http://cygwin.com/problems.html FAQ