On 24/03/2009, Paulo Vieira wrote: >> Message: 5 >> Date: Mon, 23 Mar 2009 14:08:52 -0500 >> From: "Kirk, Benjamin (JSC-EG311)" <[email protected]> >> Subject: [Libmesh-devel] FW: Upgrade for SLEPc interface in libMesh >> >> John - since you have at least used SLEPc, would you please give >> this patch >> a look? I think it is great that they did this for us!! >> >> -Ben > > Ah, great!Thank you very much Jose. I'm currently using > libMesh/PETSc/SLEPc intensively for modal analysis. I had in my todo > list to make an interface for version 3.0.0. That will save me some > hours :-) I'll be using PETSc/SLEPc v.3.0 from now on, if I find any > problems I'll report to the mailing-list. > > Btw, with version 2.3.3 (and earlier versions as well) I've always had > this output at the end of programs that use the SLEPc interface. It's > only at the end, after the results so I never bothered to see what was > causing it.
This type of error is typically due to corruption of some PETSc/SLEPc objects, that have to be destroyed at the end of the execution and so you get a sigsegv. It could be due to a heap block overrun in your main program; I don't think the source of the problem is in libMesh, because we run some test programs without problems. But anyway, what I suggest is that you try upgrading to SLEPc 3.0.0 - if you still get the same error, contact us again at the SLEPc maintenance email, [email protected] , and we will try to fix it. Jose ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
