[LLVMbugs] [Bug 17823] New: unresolved external public: virtual __thiscall ... `vbase destructor'(void)"

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=17823

            Bug ID: 17823
           Summary: unresolved external public: virtual __thiscall ...
                    `vbase destructor'(void)"
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: james.baker at bullochtech.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

In some circumstances I get linker errors starting sometime since Saturday
November 2.

LongField is a subclass of another class called Field.

Field has a virtual destructor, but LongField does not declare or define a
destructor.

Removing the virtual keyword from the parent class' destructor solves the
issue,

However, it compiled and linked on a version I build of clang/llvm on Saturday
as well as in Visual C++, and Embarcadero C++ with the destructor of the parent
class set as virtual. 

Here is a sample of the link output:


INPUT.LIB(field.obj) : error LNK2001: unresolved external symbol "public:
virtual __thiscall LongField::`vbase destructor'(void)" (??_DLongField@@UAE at XZ)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20131105/b570a5c3/attachment.html>