There is another case where calling a member method can segfault. It's the
case where the object you are calling the method on is NULL. It's quite
possible that you can start executing a member method on a NULL object
until it needs to actually work with the data. Your program won't
necessarily cra
On Tue, May 10, 2016 at 11:47 AM, Lorenzo Zanon
wrote:
> Hello,
>
> Calling empty() on the DenseVector is causing the segfault. If I
> copy the DenseVector into a std::vector, then it's fine.
>
Calling empty() on a DenseVector just calls empty() on the underlying _val,
which is a std::vector. I
Hello,
Calling empty() on the DenseVector 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 li
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 "
On Tue, May 10, 2016 at 8:16 AM, Lorenzo Zanon
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:
>
>
On Tue, 10 May 2016, Lorenzo Zanon wrote:
> 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.
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_indic
