search for: removegarbageobject

...In function `llvm::LeakDetector::addGarbageObject(llvm::Value const*)': /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to `llvm::LeakDetector::addGarbageObjectImpl(llvm::Value const*)' /home/kgibbs/CS321/CVS/llvm/lib/Debug/vmcore.o(.gnu.linkonce.t._ZN4llvm12Lea kDetector19removeGarbageObjectEPKNS_5ValueE+0xd): In function `llvm::LeakDetector::removeGarbageObject(llvm::Value const*)': /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to `llvm::LeakDetector::removeGarbageObjectImpl(llvm::Value const*)' /home/kgibbs/CS321/CVS/llvm/lib/Debug/vmcore.o(.gnu.linkonce.t...

...le.cpp GlobalVariable *ilist_traits<GlobalVariable>::createSentinel() { GlobalVariable *Ret = new GlobalVariable(Type::getInt32Ty(getGlobalContext()), false, GlobalValue::ExternalLinkage); // This should not be garbage monitored. LeakDetector::removeGarbageObject(Ret); return Ret; } GlobalAlias *ilist_traits<GlobalAlias>::createSentinel() { GlobalAlias *Ret = new GlobalAlias(Type::getInt32Ty(getGlobalContext()), GlobalValue::ExternalLinkage); // This should not be garbage monitored. LeakDetector::removeGarb...

...t the asmwriter isn't handling the "broken" LLVM IR very well. :( > What I can't figure out is where the message comes from and why. Basically it's because a BasicBlock has not be inserted into a function. If you want to FORCE this to be acceptable, use the LeakDetector::removeGarbageObject method in Support/LeakDetector.h This is yet another "helpful" LLVM debugging tool, pointing out a silly bug. :) -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

...Detector::addGarbageObject(llvm::Value const*)': > > /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to > `llvm::LeakDetector::addGarbageObjectImpl(llvm::Value const*)' > > /home/kgibbs/CS321/CVS/llvm/lib/Debug/vmcore.o(.gnu.linkonce.t._ZN4llvm12LeakDetector19removeGarbageObjectEPKNS_5ValueE+0xd): > In function `llvm::LeakDetector::removeGarbageObject(llvm::Value const*)': > > /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to > `llvm::LeakDetector::removeGarbageObjectImpl(llvm::Value const*)' > > /home/kgibbs/CS321/CVS/llvm/lib/...

I have a "first version" of Stacker up and running. Structurally its a lot like llvm-as. When I run it, I get: Leaked objects found: after running pass 'Function Pass Manager' LLVM Value subclasses leaked: Note that the supposed list of "LLVM Value subclasses leaked" is empty. Its followed up by a SIGSEGV at AsmWriter.cpp:754 presumably because I have a BasicBlock

...m/IR/LeakDetector.h > +++ b/include/llvm/IR/LeakDetector.h > @@ -79,6 +79,17 @@ struct LeakDetector { > #endif > } > > + static void addGarbageObject(const MDNode *Object) { > +#ifndef NDEBUG > + addGarbageObjectImpl(Object); > +#endif > + } > + static void removeGarbageObject(const MDNode *Object) { > +#ifndef NDEBUG > + removeGarbageObjectImpl(Object); > +#endif > + } > + > private: > // If we are debugging, the actual implementations will be called... > static void addGarbageObjectImpl(const Value *Object); >> >> >>...

...lue const*)': > > > > /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to > > `llvm::LeakDetector::addGarbageObjectImpl(llvm::Value const*)' > > > > > /home/kgibbs/CS321/CVS/llvm/lib/Debug/vmcore.o(.gnu.linkonce.t._ZN4llvm12L > eakDetector19removeGarbageObjectEPKNS_5ValueE+0xd): > > In function `llvm::LeakDetector::removeGarbageObject(llvm::Value > const*)': > > > > /usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to > > `llvm::LeakDetector::removeGarbageObjectImpl(llvm::Value const*)' > > > >...

...ething...) > > > > <0001-IR-Detect-Metadata-leaks-separately-from-generic-obj.patch> > > Zalman also had a reproduction, and he's been able to track it down to > an `addGarbageObject()` call from `MachineBasicBlock`. It looks like > the MBB gets deallocated but `removeGarbageObject()` isn't called yet. > > CC'ing him here so he can join the thread once he's gotten a little > further. > > BTW, if this is blocking anyone, I can commit the patch I attached to > my previous email (or you can apply it locally). I think it's probably > the ri...

> On 2014 Dec 10, at 14:08, Tom Stellard <tom at stellard.net> wrote: > > On Wed, Dec 10, 2014 at 11:21:08AM -0800, Duncan P. N. Exon Smith wrote: >> >>> On 2014 Dec 10, at 08:40, Tom Stellard <tom at stellard.net> wrote: >>> >>> On Tue, Dec 09, 2014 at 09:22:16PM -0800, Duncan P. N. Exon Smith wrote: >>>> The `Metadata`/`Value`