too many environment variables on self-compiled xar archiver

too many environment variables on self-compiled xar archiver

[Michael Stellar]

Hello,

I am getting the following when running my self-compiled xar 1.6.1 archiver

gdb xar

Starting program: /usr/local/bin/xar
[New Thread 12044.0x1f54]
[New Thread 12044.0xfc8]
[New Thread 12044.0x2dcc]
[New Thread 12044.0x2cd8]
[New Thread 12044.0x2d58]
      1 [main] xar 12044 C:\cygwin\usr\local\bin\xar.exe: *** fatal
error - internal error reading the windows environment - too many
environment variables?
    739 [main] xar 12044 cygwin_exception::open_stackdumpfile: Dumping
stack trace to xar.exe.stackdump
[Thread 12044.0x2dcc exited with code 256]
[Thread 12044.0xfc8 exited with code 256]
[Thread 12044.0x2cd8 exited with code 256]
[Inferior 1 (process 12044) exited with code 0400]

My env variables is here https://pastebin.com/NrWKuaSC , i have tried
to unset some of the long variables but the error still persist.

Also i have already tried using latest cygwin snapshot.

The compiled file is hosted in here :
https://www.dropbox.com/s/07439wwd7ayqy35/xar.zip?dl=0

the xar was compiled with latest boringssl compile on mingw32
statically linked with libmsvcrt.a mingw32 version.

Cheers,


Michael

--
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

Re: too many environment variables on self-compiled xar archiver

[Brian Inglis]

On 2017-05-23 16:30, Michael Stellar wrote:
> I am getting the following when running my self-compiled xar 1.6.1 archiver
> gdb xar
> Starting program: /usr/local/bin/xar
> [New Thread 12044.0x1f54]
> [New Thread 12044.0xfc8]
> [New Thread 12044.0x2dcc]
> [New Thread 12044.0x2cd8]
> [New Thread 12044.0x2d58]
>       1 [main] xar 12044 C:\cygwin\usr\local\bin\xar.exe: *** fatal
> error - internal error reading the windows environment - too many
> environment variables?
>     739 [main] xar 12044 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to xar.exe.stackdump
> [Thread 12044.0x2dcc exited with code 256]
> [Thread 12044.0xfc8 exited with code 256]
> [Thread 12044.0x2cd8 exited with code 256]
> [Inferior 1 (process 12044) exited with code 0400]
> 
> My env variables is here https://pastebin.com/NrWKuaSC , i have tried
> to unset some of the long variables but the error still persist.

Did you notice this entry and does anyone know where this comes from?
	!C:=C:\cygwin\bin

Another poster found a problem with non-ascii accented initial letters
in the environment variable name - perhaps this is the same problem?

If Cygwin environment setup has a problem with an environment variable
name or contents, it should either ignore it, copy it, or convert it to
Cygwin format, but it seems to be stumbling, when it should just be
ignoring it and skipping to the next variable.

Try removing that environment variable, either from the Control Panel,
or directly in regedit if necessary.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: too many environment variables on self-compiled xar archiver

[Michael Stellar]

Hello Brian,

        Appreciated the reply, tried to search "!C:" on registry or
searching for "!C:" in all files (*.*) content on c:\cygwin or using
tools like rapidee (to edit env variables), and the result is i could
not found it!.
Looks like it's being added by either the bash shell? itself or
something else?. The only i could found is "%{!S:%{!c:%e-c or -S
required for Ada}}" inside c++.exe, cpp.exe, g++.exe, gcc.exe.

Btw my environment is latest cygwin x86, windows 10 x64 creator
update, visual studio 2015 and & 2017 installed, gcc and g++ mingw x86
and x64 installed. Latest cygwin snapshot.


Cheers,



On Wed, May 24, 2017 at 9:53 AM, Brian Inglis
<Brian.Inglis@systematicsw.ab.ca> wrote:
> On 2017-05-23 16:30, Michael Stellar wrote:
>> I am getting the following when running my self-compiled xar 1.6.1 archiver
>> gdb xar
>> Starting program: /usr/local/bin/xar
>> [New Thread 12044.0x1f54]
>> [New Thread 12044.0xfc8]
>> [New Thread 12044.0x2dcc]
>> [New Thread 12044.0x2cd8]
>> [New Thread 12044.0x2d58]
>>       1 [main] xar 12044 C:\cygwin\usr\local\bin\xar.exe: *** fatal
>> error - internal error reading the windows environment - too many
>> environment variables?
>>     739 [main] xar 12044 cygwin_exception::open_stackdumpfile: Dumping
>> stack trace to xar.exe.stackdump
>> [Thread 12044.0x2dcc exited with code 256]
>> [Thread 12044.0xfc8 exited with code 256]
>> [Thread 12044.0x2cd8 exited with code 256]
>> [Inferior 1 (process 12044) exited with code 0400]
>>
>> My env variables is here https://pastebin.com/NrWKuaSC , i have tried
>> to unset some of the long variables but the error still persist.
>
> Did you notice this entry and does anyone know where this comes from?
>         !C:=C:\cygwin\bin
>
> Another poster found a problem with non-ascii accented initial letters
> in the environment variable name - perhaps this is the same problem?
>
> If Cygwin environment setup has a problem with an environment variable
> name or contents, it should either ignore it, copy it, or convert it to
> Cygwin format, but it seems to be stumbling, when it should just be
> ignoring it and skipping to the next variable.
>
> Try removing that environment variable, either from the Control Panel,
> or directly in regedit if necessary.
>
> --
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>
> --
> 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
>

--
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

Re: too many environment variables on self-compiled xar archiver

[Michael Stellar]

Tried, on 1 different machine without vs 2015 and vs 2017 installed on
it, pretty much minimum env variables, getting the same result,
probably it's a bug in the cygwin runtime?,

does anyone or cygwin developer have other clue?.

On Wed, May 24, 2017 at 2:42 PM, Michael Stellar
<vortexilation@gmail.com> wrote:
> Hello Brian,
>
>         Appreciated the reply, tried to search "!C:" on registry or
> searching for "!C:" in all files (*.*) content on c:\cygwin or using
> tools like rapidee (to edit env variables), and the result is i could
> not found it!.
> Looks like it's being added by either the bash shell? itself or
> something else?. The only i could found is "%{!S:%{!c:%e-c or -S
> required for Ada}}" inside c++.exe, cpp.exe, g++.exe, gcc.exe.
>
> Btw my environment is latest cygwin x86, windows 10 x64 creator
> update, visual studio 2015 and & 2017 installed, gcc and g++ mingw x86
> and x64 installed. Latest cygwin snapshot.
>
>
> Cheers,
>
>
>
> On Wed, May 24, 2017 at 9:53 AM, Brian Inglis
> <Brian.Inglis@systematicsw.ab.ca> wrote:
>> On 2017-05-23 16:30, Michael Stellar wrote:
>>> I am getting the following when running my self-compiled xar 1.6.1 archiver
>>> gdb xar
>>> Starting program: /usr/local/bin/xar
>>> [New Thread 12044.0x1f54]
>>> [New Thread 12044.0xfc8]
>>> [New Thread 12044.0x2dcc]
>>> [New Thread 12044.0x2cd8]
>>> [New Thread 12044.0x2d58]
>>>       1 [main] xar 12044 C:\cygwin\usr\local\bin\xar.exe: *** fatal
>>> error - internal error reading the windows environment - too many
>>> environment variables?
>>>     739 [main] xar 12044 cygwin_exception::open_stackdumpfile: Dumping
>>> stack trace to xar.exe.stackdump
>>> [Thread 12044.0x2dcc exited with code 256]
>>> [Thread 12044.0xfc8 exited with code 256]
>>> [Thread 12044.0x2cd8 exited with code 256]
>>> [Inferior 1 (process 12044) exited with code 0400]
>>>
>>> My env variables is here https://pastebin.com/NrWKuaSC , i have tried
>>> to unset some of the long variables but the error still persist.
>>
>> Did you notice this entry and does anyone know where this comes from?
>>         !C:=C:\cygwin\bin
>>
>> Another poster found a problem with non-ascii accented initial letters
>> in the environment variable name - perhaps this is the same problem?
>>
>> If Cygwin environment setup has a problem with an environment variable
>> name or contents, it should either ignore it, copy it, or convert it to
>> Cygwin format, but it seems to be stumbling, when it should just be
>> ignoring it and skipping to the next variable.
>>
>> Try removing that environment variable, either from the Control Panel,
>> or directly in regedit if necessary.
>>
>> --
>> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>>
>> --
>> 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
>>

--
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

Re: too many environment variables on self-compiled xar archiver

[Andrey Repin]

Greetings, Brian Inglis!

> On 2017-05-23 16:30, Michael Stellar wrote:
>> I am getting the following when running my self-compiled xar 1.6.1 archiver
>> gdb xar
>> Starting program: /usr/local/bin/xar
>> [New Thread 12044.0x1f54]
>> [New Thread 12044.0xfc8]
>> [New Thread 12044.0x2dcc]
>> [New Thread 12044.0x2cd8]
>> [New Thread 12044.0x2d58]
>>       1 [main] xar 12044 C:\cygwin\usr\local\bin\xar.exe: *** fatal
>> error - internal error reading the windows environment - too many
>> environment variables?
>>     739 [main] xar 12044 cygwin_exception::open_stackdumpfile: Dumping
>> stack trace to xar.exe.stackdump
>> [Thread 12044.0x2dcc exited with code 256]
>> [Thread 12044.0xfc8 exited with code 256]
>> [Thread 12044.0x2cd8 exited with code 256]
>> [Inferior 1 (process 12044) exited with code 0400]
>> 
>> My env variables is here https://pastebin.com/NrWKuaSC , i have tried
>> to unset some of the long variables but the error still persist.

> Did you notice this entry and does anyone know where this comes from?
>         !C:=C:\cygwin\bin

This is coming from CMD, and denotes current working directory on an indicated
drive.

> Another poster found a problem with non-ascii accented initial letters
> in the environment variable name - perhaps this is the same problem?

> If Cygwin environment setup has a problem with an environment variable
> name or contents, it should either ignore it, copy it, or convert it to
> Cygwin format, but it seems to be stumbling, when it should just be
> ignoring it and skipping to the next variable.

> Try removing that environment variable, either from the Control Panel,
> or directly in regedit if necessary.



-- 
With best regards,
Andrey Repin
Wednesday, May 24, 2017 12:59:39

Sorry for my terrible english...


--
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

Re: too many environment variables on self-compiled xar archiver

[Hans-Bernhard Bröker]

Am 24.05.2017 um 12:01 schrieb Andrey Repin:

>> Did you notice this entry and does anyone know where this comes from?
>>          !C:=C:\cygwin\bin

> This is coming from CMD, and denotes current working directory on an indicated
> drive.

And for (most of) all the hairy details, see

https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133

If you see these, you must have printed the environment using a tool 
other than CMD itself (e.g. Cygwin's "env").

--
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

Re: too many environment variables on self-compiled xar archiver

[Andrey Repin]

Greetings, Hans-Bernhard Bröker!

> Am 24.05.2017 um 12:01 schrieb Andrey Repin:

>>> Did you notice this entry and does anyone know where this comes from?
>>>          !C:=C:\cygwin\bin

>> This is coming from CMD, and denotes current working directory on an indicated
>> drive.

> And for (most of) all the hairy details, see

> https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133

> If you see these, you must have printed the environment using a tool 
> other than CMD itself (e.g. Cygwin's "env").

Yes, as evident by the Cygwin paths in $PATH.


-- 
With best regards,
Andrey Repin
Thursday, May 25, 2017 16:29:47

Sorry for my terrible english...
--
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

Re: too many environment variables on self-compiled xar archiver

[Brian Inglis]

On 2017-05-24 15:18, Hans-Bernhard Bröker wrote:
> Am 24.05.2017 um 12:01 schrieb Andrey Repin:
> 
>>> Did you notice this entry and does anyone know where this comes from?
>>>          !C:=C:\cygwin\bin
> 
>> This is coming from CMD, and denotes current working directory on an
>> indicated
>> drive.
> 
> And for (most of) all the hairy details, see
> 
> https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133
> 
> If you see these, you must have printed the environment using a tool
> other than CMD itself (e.g. Cygwin's "env").

Or as comment
https://blogs.msdn.microsoft.com/oldnewthing/20100506-00/?p=14133#comment-830913
says, in cmd type
	set "
to see all environment variables including those starting with "=".

So the above is Cygwin "cleaning" the inherited cmd environment which
contains =<d>:=<d>:\<wd> for each mapped drive, and some other legacy
compatible information, by changing the leading "=" to "!", so it can
restore it for child process environments.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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