Thanks Sean. I'm using Petsc 3.2-p6 along with ParMetis 4.0.2. Since this was not supported with 3.2-p6, and previous versions had bugs, I built parmetis myself and used --with-parmetis-include and --with-parmetis-lib flags to build petsc.
Should I switch to petsc-dev? On Mon, Apr 9, 2012 at 8:27 PM, Sean Farley <sean at mcs.anl.gov> wrote: > -on_error_attach_debugger does not start the debugger. I traced it upto >> the following call: MatPartitioningApply(). It runs fine up until that >> function call and then gives the error. >> >> Also, to make things even look more weird, I got the following once I was >> running it: >> >> Key 10176 not found! >> INTERNAL ERROR: Invalid error class (66) encountered while returning from >> PMPI_Waitall. Please file a bug report. >> >> Do you happen to know what that could mean? The funny thing is, it only >> happened once! >> > > This is a parmetis error from libparmetis/util.c:78 and not with petsc > (well, at least, not directly an error from petsc). How did you build > parmetis? Which parmetis version and which petsc version are you running? > You'll probably have to send configure.log to petsc-maint at mcs.anl.gov. > > By the way, the relevant function that is having the error is: > > /************************************************************************* > * This function does a binary search on an array for a key and returns > * the index > **************************************************************************/ > idx_t BSearch(idx_t n, idx_t *array, idx_t key) > > ... which doesn't help much unless you can step into the debugger and set > a breakpoint here to give a traceback. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120409/1886d7af/attachment.htm>
