[petsc-users] question about partitioning usage

[Dominik Szczerba]

> So ParMETIS crashes on the hostile platform where it is slow to debug, fine.
>
> But your code is calling it in cases where it doesn't crash, so why not run
> the same code in your friendly environment and set a breakpoint in
> MatPartitioningApply() (or even the ParMETIS routine where the assert is
> failing) so that you can find out where else it is being called from. This
> should take about 10 seconds.

It will take several minutes till xterm gdb windows will pop up, till
I will manage to type "c+ENTER" into 64 windows on my 1024x768
quadcore, and then till I find the right window where the executions
stopped - but yes, it is definitely doable, and I already did that, as
posted separately. The point I was trying to clarify here was if one
at all expects calls to parmetis (or equivalent) other than
MatPartitioning after it was destroyed (e.g. for some hidden internal
matrix partitioning later). I just wanted to hear a hard yes or no.

Thanks,
Dominik