Hi all, I'm sorry if that sounded too rash, I mean that g++ 5.2 -fsanitize=address (AddressSanitizer) claimed lines 82 and 90 as sources of memory leaks, which through some kind of interaction I don't understand (yet), my patch could also have caused, even though I didn't change any constructor in my patch.
Best regards, mabri P.S. Please disregard the foreign language in my last post, that was through using some "quick answer" feature in a mis-configured mail client, it's corrected here. > Matthew Brincke <ma...@mailbox.org> has written on 13 March 2017 at 00:00: > > Hi all, > > I found now that PdfOutlines.cpp lines 82 and 90 are highly suspect memory > leaks, not anywhere I touched. > > Best regards, mabri > > > Matthew Brincke <ma...@mailbox.org> has written on 12 March 2017 at 00:48: > > > > > > Hi all, > > > > one addendum: that's what I've come up with up to now, > > I've just seen there are still some indirect memory leaks > > claimed by g++ 5.2 -fsanitize=address in the non-happypath case > > in my tests (just partial-linking to my PdfOutlines version, > > otherwise using the Debian stretch libpodofo0.9.4 due to security policy). > > I don't know if I'll have time to work on those, if I'm not posting > > next week or so, could you please take it up from there? > > > > Best regards, mabri ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
