Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the compiler generate undefined symbol WHAT__K9BAD_ALLOCXV?

April 26, 2017compiler symbol undefined

0

Posted

Why does the compiler generate undefined symbol WHAT__K9BAD_ALLOCXV?

1 Answer

0

Posted

The library object file bv_inst.obj, which was created incorrectly, contains an undefined symbol bad_alloc::what(). If you #include , some inline functions in the bitvector class (at the bottom of the vector header file) cause the linker to require references from bv_inst.obj. The unresolved error occurs when the linker includes that object file. Though disconcerting, the linker error is harmless. S: This problem has been fixed in Version 6.0 of the Standard Library. W: In most cases, you can ignore the linker message. It is a problem only if a shareable image is being created (because any application linking against it also receives the warning).