Has anyone attempted to analyze this issue using valgrind? (I have not
yet). It smells like heap or stack corruption to me.
On Fri, Feb 10, 2017 at 5:37 AM, Sandro Mani <[email protected]> wrote:
>
>
> On 08.02.2017 11:21, Sandro Mani wrote:
> >
> >
> > However I can't reproduce it with the static library though, so it is
> > definitely related to the shared library.
> >
> Hi
> Dropping -std=c++98 "fixes" the issue for me. Is there a reason for
> using -std=c++98?
>
> Sandro
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Podofo-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Podofo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/podofo-users
