OpenSAML user discussion

[Chris Card <>]

> > > You're always responsible for an
> > > XMLObject returned from a Builder, or from the static build methods.
> > >
> > Thanks, it's clear now, but is that stated anywhere in the docs?
>
> It's alluded to in the wiki, but I added it to all the builder method API
> docs.
thanks Scott.

I've eliminated all the definite leaks reported by valgrind now, except for a couple originating from IMPL_STRING_ATTRIB which I have no control over:

==4416== 76 bytes in 1 blocks are definitely lost in loss record 57 of 83
==4416==    at 0x4A05974: operator new(unsigned long) (vg_replace_malloc.c:220)
==4416==    by 0x3D9BFCDC6B: xercesc_3_0::MemoryManagerImpl::allocate(unsigned long) (in /usr/lib64/libxerces-c-3.0.so)
==4416==    by 0x5A4BBBD: xmltooling::AbstractXMLObject::prepareForAssignment(unsigned short*, unsigned short const*) (XMLString.hpp:1558)
==4416==    by 0x50888A9: opensaml::saml2::SubjectConfirmationImpl::setMethod(unsigned short const*) (Assertions20Impl.cpp:785)
==4416==    by 0x5A5E0C0: xmltooling::AbstractXMLObjectUnmarshaller::unmarshallAttributes(xercesc_3_0::DOMElement const*) (AbstractXMLObjectUnmarshaller.cpp:156)
==4416==    by 0x5A5DBCA: xmltooling::AbstractXMLObjectUnmarshaller::unmarshall(xercesc_3_0::DOMElement*, bool) (AbstractXMLObjectUnmarshaller.cpp:66)
==4416==    by 0x5A51CD8: xmltooling::XMLObjectBuilder::buildFromElement(xercesc_3_0::DOMElement*, bool) const (XMLObjectBuilder.cpp:57)
....

and a similar from from opensaml::saml2p::StatusCodeImpl::setValue(unsigned short const*)

Are these anything to worry about?

Chris