Re: [Getfem-users] Errors in Getfem debug mode due to iterators out of range.

[Teresa Pinheiro]

Thank you for your reply Andriy.

I can't do this because I use some precompiled 3rd party libraries and as you've said, this would throw some linking and runtime errors..

Maybe I could try to fix all loops using iterators ( there are a lot ) but I understand that sometimes this is not straightforward and I don't want to break anything...

Best regards, 

Teresa

2015-03-11 13:31 GMT+01:00 Andriy Andreykiv <address@hidden>:

Dear Teresa,

We had the same problem on Windows, so, as a result, while building in the debug mode we were linking against

non-debug runtime libraries. 

On MSVC go to project properties->ConfigurationProperties->C/C++->Code Generation and choose, for instance Runtime Library to Multi-threaded(/MT).

You should use this option on all libraries that you are linking otherwise you'll have linking conflicts

Best regards,

                    Andriy

On 11 March 2015 at 13:05, Teresa Pinheiro <address@hidden> wrote:

Hi,

I'm having problems with Getfem 4.3 compiled in Windows 7, VS2013 in Debug mode.

In Debug mode, there are some runtime checks ( _HAS_ITERATOR_DEBUGGING -  https://msdn.microsoft.com/en-us/library/aa985939.aspx ) that makes libgetfem.dll fail. It occurs when an iterator has reached the end and Getfem algorithm tries to increase it. 

This behaviour is present in several methods of Getfem. 

In VS2013 Release mode and in GNU/Linux + GCC works fine. 

I can't change _HAS_ITERATOR_DEBUGGING because it would mismatch the iterator debugging mode with other 3rd libraries that I use and fail.

My questions are: Is there someone compiling in Windows with the same problem? How can this be fixed?

Thank you very much. 

Teresa

_______________________________________________
Getfem-users mailing list
address@hidden
https://mail.gna.org/listinfo/getfem-users