OpenSAML user discussion

[Chris Card <>]

> > response_ = dynamic_cast<Response*>(xo.get())->cloneResponse();
> >
> > while in another scope I tried to verify the signature taken from the
> > assertion in response_. I assumed that since I'd called cloneResponse()
> it
> > wouldn't matter that xo was destroyed at the end of the above scope, but
> in
> > fact that caused the problem calculating the digest. If I extend xo's
> > lifetime the digest calculation is fine.
>
> I can't explain that, it should work fine. You have a clone, so it's totally
> disconnected from the original.
>
> There has to be a serious bug if the original object has any relevance.

At least I've got it working now, but I'm a bit concerned if there's a bug lurking there.

Also, I'm worried about memory leaks - it's not clear to me which objects I need to delete and which
are handled by the library. I've run my program under valgrind and it's picked up a few leaks, but
when I tried to fix them by adding explicit deletes in my code, in some cases the program core dumped (in XMLString::release()).

Are there any guidelines for memory management when using opensaml?

Chris