public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: too many environment variables on self-compiled xar archiver
Date: Wed, 24 May 2017 03:34:00 -0000	[thread overview]
Message-ID: <55609c2e-6bc5-1819-8342-815a0d79e51d@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAL5LfdTT-FQpZCBEr=r2ntU9NibGF2hRU=e6fd_R-4n39RKwng@mail.gmail.com>

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

  reply	other threads:[~2017-05-24  2:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 22:59 Michael Stellar
2017-05-24  3:34 ` Brian Inglis [this message]
2017-05-24  7:52   ` Michael Stellar
2017-05-24 10:05     ` Michael Stellar
2017-05-24 10:05   ` Andrey Repin
2017-05-24 23:36     ` Hans-Bernhard Bröker
2017-05-25 14:50       ` Andrey Repin
2017-05-25 17:37       ` Brian Inglis

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=55609c2e-6bc5-1819-8342-815a0d79e51d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).