Some objects such as PETSC_VIEWER_STDOUT_WORLD cannot be destroyed by users.

Reported-by: maitri ksh <maitri.ksh@gmail.com>

Sys: Introduce -on_error_malloc_dump and PETSC_ERR_MEM_LEAK

To avoid a malloc dump that swamps the error output of another error,
this makes calling `PetscMallocDump()` in the error handlers opt-in,

Sys: Introduce -on_error_malloc_dump and PETSC_ERR_MEM_LEAK

To avoid a malloc dump that swamps the error output of another error,
this makes calling `PetscMallocDump()` in the error handlers opt-in,
with a different flag (`-on_error_malloc_dump`) from the flag for
calling `PetscMallocDump()` in `PetscFinalize()` (just `-malloc_dump`).

The addition of `PETSC_ERR_MEM_LEAK` allows for better error messages:
`~PoolAllocator()` can detect a memory leak even if the system
is not out of memory, so the error message will not say that for
`PETSC_ERR_MEM_LEAK`.

show more ...

Merge branch 'stefanozampini/no-abort' into 'main'

Cannot call PETSCABORT in traceback error handler

See merge request petsc/petsc!6747

Profiling: Add test of PetscLogEventsPause() / PetscLogEventsResume()

Profiling: Add tests of PetscLogHandler to sys/tests/ex30.c

- The pattern of events and stages is made more complicated
to test the fact that nested logging can represent nested
stages now.

- T

Profiling: Add tests of PetscLogHandler to sys/tests/ex30.c

- The pattern of events and stages is made more complicated
to test the fact that nested logging can represent nested
stages now.

- To test perfstubs without adding TAU as an optional dependency,
a dummy perfstubs tool implementation is tested.

New tests:

- 0: tests the fact that events and stages can be registered
in different orders for different processes (at least
for the default log handler: this is not true of all external tools
like MPE)

- 1: Test flamegraph (nested log handler)

- 2: Test trace log handler

- 3: Test PetscLogDump() output with actions and objects logging
Note that this test uses the "temporaries:" test key for the
dump file Log.0

- 4: Test CSV output

- 5: Test MPE log handler
MPE logging creates a .clog2 binary file. Without trying
to add a dependency to turn it into text, if we use
`strings` we can at least see if the names of the events
created in the test are in the file

- 6: Test perfstubs
Because this relies on dlsym(RTLD_DEFAULT, ...) dynamic linking, this
test can only be run on linux

show more ...

Add test of PetscValidPointer generics

Cannot call PETSCABORT in traceback error handler

Need to have test harness remove -options_left to tests that test handling of errors in tests

Commit-type: testing

When the user does not properly handle a returned error code and another error is detected, print a very useful message indicating what has happended.

Reported-by: Stefano Zampini