Remove MANSEC from makefiles it is not needed in, tutorials and tests
Merge remote-tracking branch 'origin/release'
Fix -Wzero-as-null-pointer-constant errors
Rename rules.doc and rules.utils because GitLab treats the former as a MS Word document.Thanks-to: Jed Brown
Remove DIRS variable and unneeded tabs from all makefiles since no longer neededCommit-type: housekeeping
Fix typos
Remove first and last empty lines
Sys: Do not exit in PetscTraceBackErrorHandler(); use TLS to silence non-root tracebacks
Convert all header guards to pragma once
Document better when and how -no-signal-handler should be used.Reported-by: "Graham, Aaron" <grahamam@ornl.gov>
Add static to internal functions
Sys: Introduce -on_error_malloc_dump and PETSC_ERR_MEM_LEAKTo 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_LEAKTo 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 forcalling `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 systemis 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 handlerSee merge request petsc/petsc!6747
... and apply it
Rename PetscValidPointer -> PetscAssertPointer
Deploy new PetscValidPointer, remove PetscValidXXXPointer
Cannot call PETSCABORT in traceback error handler
Manual linter fixes: sys
Lint apply: sys
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
Sadly, isatty() is not a reliable way to determine if PetscAttachDebugger() will workReported-by: Pierre Jolivet
Merge branch 'barry/2023-06-15/add-fortran-file-viewer' into 'main'Allow one to attach a PETSCVIEWERASCII to a Fortran file unitSee merge request petsc/petsc!6607
HAVE_FORTRAN should be USE_FORTRAN_BINDINGS since it is about generating the Fortran bindings, not about if the Fortran compiler exists
Fix for !6606 should not check tty if using a seperate terminal for the debuggerReported-by: Matthew Knepley
12345678910>>...23