Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Mark Hadfield <m DOT hadfield AT niwa DOT co DOT nz>
Subject:  Re: *** system shared memory version mismatch detected
Date:  Fri, 20 May 2005 11:17:39 +1200
Lines: 32
Message-ID: <d6j6or$lj$1@sea.gmane.org>
References:  <20050519203312 DOT 4B8A DOT GIULIASTRO AT tin DOT it> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050519164941 DOT 09f559a0 AT pop DOT prospeed DOT net> <20050520000509 DOT 4FC9 DOT GIULIASTRO AT tin DOT it> <428D1001 DOT 6EF8FAA7 AT dessent DOT net> <20050519225052 DOT GK13760 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
In-Reply-To: <20050519225052.GK13760@trixie.casa.cgf.cx>
X-IsSubscribed: yes

Christopher Faylor wrote:
 >Brian Dessent wrote:
>>Check the mailing list archives, I think there were some recent issues
>>relating to the way the DLL handled interlocking on initialization that
>>led to spurious cygheap mismatch errors.  Or just try a snapshot.
> 
> 
> That would only happen when multiple cygwin processes were started from
> non-cygwin processes.
> 
> Surely, the OP would not have failed to mention that crucial piece of
> data.

Surely not! Actually the OP has not given much info on what he did to 
trigger the error.

Exceeding the g77 160 MiB limit has been observed to trigger "cygheap 
base mismatch" error messages, with the advice, "This problem is 
probably due to using incompatible versions of the cygwin DLL." (It wasn't.)

See

   http://sourceware.org/ml/cygwin/2005-04/msg00305.html

Now this isn't the same error as reported by the OP, but I think it is 
clear that, with some recent versions of the Cygwin DLL, memory 
corruption can occur and can produce misleading error messages.

-- 
Mark Hadfield            "Ka puwaha te tai nei, Hoea tatou"
m DOT hadfield AT niwa DOT co DOT nz
National Institute for Water and Atmospheric Research (NIWA)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/