On Tue, May 10, 2016 at 8:16 AM, Lorenzo Zanon <[email protected]> wrote:
> Hello, > > After a libMesh update, I have to adjust my code to the > explicit/implicit separation in RBEIMConstruction. Now, in my overridden > function of RBEIMConstruction::truth_solve I get an error at the > following line: > > rhs->add_vector(context.get_elem_residual(), > context.get_dof_indices()); > > The crash happens at the line: > > if (!v.empty()) > > in the function add_vector (see debugger below). > > If I convert context.get_elem_residual() from a DenseVector to a > std::vector, I do not have any error. If I run RB-example4 (EIM), there > is also no error. > > Can anybody see what is going wrong with my DenseVector? > I don't see how calling empty() on a std::vector could ever segfault, unless there was something wrong with your build/compiler. Since you mention updating libmesh recently, could this be the issue? The line numbers in your stack trace don't exactly line up with the master version of libmesh... Can you let us know exactly which version you are using? Also, if you can share the code that actually segfaults we can see if we can reproduce it... -- John ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
