Hello, Calling empty() on the DenseVector<Number> is causing the segfault. If I copy the DenseVector into a std::vector, then it's fine.
How can I see if there is something wrong with my build/compiler? Everything runs fine apart from that error. The libMesh version is 0.9.5 (according to the first line of the NEWS file). The lines I sent come from a debug in dbg-mode with gdb. I can share the code, but there are several files. It looks like rhs->add_vector() is failing with any DenseVector<Number>, crashing at the check empty(). Thanks :) Lorenzo On 5/10/16 5:08 PM, Roy Stogner wrote: > > On Tue, 10 May 2016, John Peterson wrote: > >> I don't see how calling empty() on a std::vector could ever segfault, > > The std::vector could be in an inconsistent state, if it was free'd > but you're still accessing it from a dangling reference. I suppose in > that case it would segfault from a simple "p v" in gdb too, though. > >> unless there was something wrong with your build/compiler. Since you >> mention updating libmesh recently, could this be the issue? > > That's definitely a good guess. > --- > Roy ------------------------------------------------------------------------------ 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
