Community
cancel
Showing results for 
Search instead for 
Did you mean: 
76 Views

Bug with std::locale in debug builds

Hi all,

It seems the win32 debug ( and x64 ) libs are missing std::runtime_error c'tor and d'tor. Or at least something very odd is happening. Put the following lines in a cpp file, in a generic windows dll project and do a debug build. Two linker errors will pop up ( see below ). Compile it in Release and all is good. This is a huge blocker for us, and need a fix or work-around ASAP. It happens in 11.1.034 and 046 with Visual Studio 2008 sp1.


/************/
#include

using namespace std;

locale format_locale ("C");


1>test.obj : error LNK2001: unresolved external symbol "public: __cdecl std::runtime_error::runtime_error(class std::runtime_error const &)" (??0runtime_error@std@@QEAA@AEBV01@@Z)
1>test.obj : error LNK2001: unresolved external symbol "public: virtual __cdecl std::runtime_error::~runtime_error(void)" (??1runtime_error@std@@UEAA@XZ)
1

------------------
Robert Haskett
0 Kudos
6 Replies
Mark_S_Intel1
Employee
76 Views

Thanks for the problem report. I was able to reproduce the error. We will look into this issue and let you know when the issue is resolved.

Mark Sabahi
Intel Developer Support
dritter29
Beginner
76 Views


Has this issue been addressed? If not, is there a projected fix date? Has anyone found a workaround? We are also experiencing this same linker issue with debug builds.

Thanks,
David Ritter

Mark_S_Intel1
Employee
76 Views

David,

This issue has not been resolved, yet, and a projected fix date is not available at this time. The example provided in the original report builds without errors at /MTd instead of /MDd. Would using /MTd work for you?

Thanks,
--mark
dritter29
Beginner
76 Views


Hello Mark,

Unfortunately we are unable to use /MTd in our project due to link incompatibility issues with a shared library we build and a conflict with including both the shared and static MSVC runtimes.

Is there a bug number that this issue has been assigned so I can look for it in future ICL update releases?

Thank you for your help,
Dave
Mark_S_Intel1
Employee
76 Views

Thetracking number for this issue is DPD200140455.

The development believe they have resolved this issue.The fix will be available in the next compiler update with build date of January 22 or higher. We will let you know when a compiler update with the fix becomes available.

Thanks,
--mark

Mark_S_Intel1
Employee
76 Views

This issue has been resolved in the compiler package w_cproc_p_11.1.060 build 20100203 or higher.

--mark

Reply