From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.10/1.7.11: .Net programs started from a cygwin console may fail.
Date: Tue, 28 Feb 2012 14:15:00 -0000 [thread overview]
Message-ID: <20120228125601.GC23440@calimero.vinschen.de> (raw)
In-Reply-To: <4F4BA00E.2020806@prover.com>
On Feb 27 16:23, Andres Martinelli wrote:
> Hi Cygwin,
>
> Many .Net programs that use to run correctly from a cygwin 1.7.9
> console started throwing exceptions after updating to versions
> 1.7.10/1.7.11. I have noticed this problem on machines running
> Windows XP and Vista (32bits).
>
> I attach a very small example that triggers the bug. The example is
> written in C#, and requires the .Net framework versions 2.0 or 3.5.
>
> How to reproduce:
>
> 1) Compile the example with
> csc bug.cs
>
> The c# compiler (csc), can be usually found in
> C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe
> or C:\Windows\Microsoft.NET\Framework\v3.5\csc.exe
>
> 2) Run the resulting bug.exe from a cygwin 1.7.10/1.7.11 console. It
> throws an exception.
>
> 3) Run bug.exe from a native windows console (or a cygwin 1.7.9
> console). It runs without producing any output, and without throwing
> any exceptions.
>
> Be aware that the bug is not triggered if the example is compiled
> with the .Net framework 4.0.
The problem is that I have not the faintest insight into .Net. This is
an application written in a language I don't know, using a class library
I don't know, using a compiler I don't know. And the executable isn't
even a Cygwin application so it doesn't call Cygwin functions. So I
have no idea what problem this application has. What on earth is it
trying to tell me?
Unhandled Exception: System.ArgumentException: Item has already been added. Key
in dictionary: 'tmp' Key being added: 'tmp'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
at System.Collections.Hashtable.Add(Object key, Object value)
at System.Collections.Specialized.StringDictionary.Add(String key, String value)
[etc.]
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
next prev parent reply other threads:[~2012-02-28 12:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 16:54 Andres Martinelli
2012-02-28 14:15 ` Corinna Vinschen [this message]
2012-02-28 14:18 ` Jon Clugston
2012-02-28 14:50 ` Corinna Vinschen
2012-02-28 21:42 ` David Sastre Medina
2012-02-28 23:05 ` Corinna Vinschen
2012-02-29 9:42 ` Corinna Vinschen
2012-02-29 1:36 ` Andrey Repin
2012-02-29 9:47 ` Corinna Vinschen
2012-02-29 12:39 ` Andrey Repin
2012-02-29 12:49 ` Earnie Boyd
2012-02-29 14:51 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2012-03-12 19:51 James Johnston
2012-03-13 19:58 ` David Sastre Medina
2012-03-01 18:49 Matt Seitz (matseitz)
2012-03-01 18:17 Matt Seitz (matseitz)
2012-03-01 18:41 ` Corinna Vinschen
2012-02-29 22:47 Matt Seitz (matseitz)
2012-03-01 10:09 ` Corinna Vinschen
2012-02-27 16:12 Andres Martinelli
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=20120228125601.GC23440@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).