History log of /petsc/src/sys/tests/output/ex66_1.out (Results 1 – 6 of 6)
Revision Date Author Comments
# 9c861a52 07-Aug-2023 Satish Balay <balay@mcs.anl.gov>

Merge branch 'tisaac/feature-malloc-dump-finalize' into 'main'

Sys: Introduce -on_error_malloc_dump and PETSC_ERR_MEM_LEAK

See merge request petsc/petsc!6745


# 9beb8f72 07-Aug-2023 Toby Isaac <toby.isaac@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 ...


# d3f910d4 28-Jul-2023 Satish Balay <balay@mcs.anl.gov>

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

Cannot call PETSCABORT in traceback error handler

See merge request petsc/petsc!6747


# 4e29e845 21-Jul-2023 Stefano Zampini <stefano.zampini@gmail.com>

Cannot call PETSCABORT in traceback error handler


# 479160d7 12-Jul-2023 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2023-07-02/nice-error-message-when-first-error-is-not-properly-handled' into 'main'

When the user does not properly handle a returned error code and another error...

See merge r

Merge branch 'barry/2023-07-02/nice-error-message-when-first-error-is-not-properly-handled' into 'main'

When the user does not properly handle a returned error code and another error...

See merge request petsc/petsc!6655

show more ...


# 15858b40 03-Jul-2023 Barry Smith <bsmith@mcs.anl.gov>

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