> On Mar 21, 2016, at 7:12 PM, Derek Gaston <[email protected]> wrote: > > Ah! I figured it out. The issue is UniquePtr... I still can't figure out > _why_ anyone would want one of those. In this case the problem came down > to this line: > > auto solution_vector = output_system.solution; > > Turns out that this was _stealing_ the pointer from the System! > (Personally, I think this is an interface problem... it should never be > possible to nullify a pointer inside of a libMesh object so easily!)
This mistake should only even be possible if your UniquePtr is still a std::auto_ptr. Are you configured with --enable-unique-ptr? I don't think it's an issue with the libmesh interface, it's a well-known issue with std::auto_ptr that was masked by your use of "auto". ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
