Bug 103137

Summary: [Gtk] Tools/TestWebKitAPI/Tests/WTF/MemoryInstrumentationTest.cpp fails to link
Product: WebKit Reporter: Yury Semikhatsky <yurys>
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: berto, gustavo, loislo, pfeldman, philn, xan.lopez, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 102510    
Bug Blocks:    
Attachments:
Description Flags
Failing change none

Yury Semikhatsky
Reported 2012-11-23 06:43:35 PST
Adding Tools/TestWebKitAPI/Tests/WTF/MemoryInstrumentationTest.cpp to Tools/TestWebKitAPI/GNUmakefile.am causes linker failure. Although doing the same with e.g. Tools/TestWebKitAPI/Tests/WTF/WTFSring.cpp works just fine. I originally faced this issue while working on patch for webkit.org/b/102510. Compilation started failing when I moved part of wtf/MemoryInstrumentation.h into wtf/MemoryInstrumentation.cpp (see http://queues.webkit.org/results/14899240): "ts/WTF/Programs_TestWebKitAPI_TestWTF-MemoryInstrumentationTest.o:MemoryInstrumentationTest.cpp:function typeinfo for (anonymous namespace)::InstrumentationTestImpl: error: undefined reference to 'typeinfo for WTF::MemoryInstrumentation"
Attachments
Failing change (977 bytes, patch)
2012-11-23 06:46 PST, Yury Semikhatsky 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Yury Semikhatsky
Comment 1 2012-11-23 06:46:22 PST
Created attachment 175798 [details] Failing change
Yury Semikhatsky
Comment 2 2012-11-23 07:27:27 PST
Can someone familiar with Gtk build system help me resolve the issue? Source/WTF/wtf/MemoryInstrumentation.cpp seems to be included in the same places in GNUmakefiles as Source/WTF/wtf/text/WTFString.cpp, still methods from Source/WTF/wtf/text/WTFString.cpp are accessible from Tools/TestWebKitAPI/Tests/WTF/WTFSring.cpp while those of Source/WTF/wtf/MemoryInstrumentation.cpp aren't.
Alberto Garcia
Comment 3 2013-10-09 14:29:22 PDT
Obsolete after bug 114931.
Note You need to log in before you can comment on or make changes to this bug.