Advice for debugging heap mismatches? (Win10 Insider build 14926)
Achim Gratz
Stromeko@nexgo.de
Sun Oct 2 15:09:00 GMT 2016
Tony Kelman writes:
>> Could you paste a complete sample of the error message so we can
>> determine where in the Cygwin code it's coming from?
>
> Still a problem in 14936. Folks, this could be very bad. Anyone at all
> testing the insider builds, or are we going to be blindsided when an
> update goes out to everyone that breaks cygwin?
How about you start with a sane PATH that doesn#t contain all the
Windows stuff? Set a system variable CYGWIN_NOWINPATH=true and try
again.
> Here's one:
>
> 1 [main] cp (6432) C:\cygwin64\bin\cp.exe: *** fatal error - cygheap base mismatch detected - 0x180302408/0xD92408.
> This problem is probably due to using incompatible versions of the
> cygwin DLL.
Something occupies the heap area for Cygwin, based on the low address.
What does /proc/self/maps tell you?
> And another:
>
> 0 [main] cmake 10384 child_info_fork::abort: C:\cygwin64\bin\cygintl-8.dll: Loaded to different address: parent(0x3E3680000) != child(0x190000)
Again either an address collision or some BLODA intercepting the DLL,
check the memory maps to see what might be going on.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
--
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
More information about the Cygwin
mailing list