On Tue, Feb 17, 2015 at 1:25 PM, Harshad Sahasrabudhe <[email protected]> wrote:
> Sorry about that. I'll just print the stack here. Should I be worried > about the PARMETIS error? I'll also try using 0.9.4-rc2. > I don't think the segfault has anything to do with Parmetis. It looks like the scalars are different in VecSet for the 2 processes. I > will look into that problem, it looks like a problem with my code. > > #0 0x0000003ceec32625 in raise () from /lib64/libc.so.6 > #1 0x0000003ceec33e05 in abort () from /lib64/libc.so.6 > #2 0x00002ad6d8c04102 in PetscAbortErrorHandler () from > /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 > #3 0x00002ad6d8c0200b in PetscError () from > /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 > #4 0x00002ad6d8aea8eb in VecSet () from > /home/hsahasra/NEMO5/libs/libmesh/libmesh/.libs/libmesh_dbg.so.0 > #5 0x00002ad6d7a0e106 in libMesh::PetscVector<libMesh::Real>::zero > (this=0x7fffac4ba128) at ./include/libmesh/petsc_vector.h:1023 > Looks like you are calling PetscVector::zero() from inside your residual assembly function. It's possible that the residual vector is not in the right state (not closed) when you call this... but we would have to see the rest of your code to know for sure. -- John ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
