*** system shared memory version mismatch detected

[Mark Hadfield]

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.hadfield@niwa.co.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/