Bogdan Czwartkowski admin
- Bogdan Czwartkowski
- Last Active
- Admin, Staff
Thanks Andrey, great post!
Just an extra note for working with Cygwin environment:
In Cygwin 'gcc' and 'g++' can be a UNIX-style symbolic links that point to actual compiler .exe files. For example, in my system 'g++' points (indirectly) to 'g++-4.exe' located in Cygwin's '/bin' which is C:/cygwin/bin folder on Windows.
However, C++test has to use regular Windows process API to run compiler. Windows will not understand UNIX-style sym-links that Cygwin uses. Therefore, when working with Cygwin, you should use actual .exe name of the compiler in Build Settings.
This would be, for example, 'gcc-4.exe' and 'g++-4.exe' assuming c:/cygwin/bin is part of PATH, or full path like 'c:/cygwin/bin/gcc-4.exe'.
Of course everything that Andrey wrote still applies.1
This kind of issues is going to be specific to your environment. It just that it manifests inside Insure++ library, because it monitors your application.
What I can recommend is to contact support via email@example.com, or open a support ticket in the customer portal (https://parasoft.force.com/customerportal/MyCases)1