Barry Smith writes:
> No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on
> the first 10 ranks? Not clear how to do that. Or valgrind should get a MR
> that removes this small arbitrary limitation on the number of processes. 576
> is so 2000 :-)
I don't want it
Thanks so much, Satish,
On Tue, Dec 15, 2020 at 9:33 AM Satish Balay via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> For one - I think using '--log-file=valgrind-%q{HOSTNAME}-%p.log' might
> help [to keep the logs from each process separate]
>
> And I think the TMPDIR recommendation is to
For one - I think using '--log-file=valgrind-%q{HOSTNAME}-%p.log' might help
[to keep the logs from each process separate]
And I think the TMPDIR recommendation is to have a different value for each of
the nodes [where the "pid" clash comes from] and perhaps "TMPDIR=/tmp" might
work - as this
Fande,
Did you try set TMPDIR for valgrind?
Sent from my iPhone
> On Dec 15, 2020, at 1:23 AM, Barry Smith wrote:
>
>
> No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on
> the first 10 ranks? Not clear how to do that. Or valgrind should get a MR
> that removes
No idea. Perhaps petscmpiexec could be modified so it only ran valgrind on
the first 10 ranks? Not clear how to do that. Or valgrind should get a MR that
removes this small arbitrary limitation on the number of processes. 576 is so
2000 :-)
Barry
> On Dec 14, 2020, at 11:59 PM, Fande
