Repository navigation
Name the C function and PETSc's message in PetscError - #315
Merged
Merged
Conversation
A PetscError now carries the C function the failing call went to and PETSc's text for the error, read as soon as the call fails, and prints both: "PetscError(56) from VecSetSizes: No support for this operation for this object type. Cannot change/reset vector sizes ...". Before it would only have printed "PetscError(56)". PetscError(code) and err.code work as before. Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A failing PETSc call used to surface in Julia as
PetscError(56)and nothing else; the explanation only went to stderr. The error now records the C function Julia called and PETSc's message, and prints them:PetscError(code)anderr.codeare unchanged.@chktakes the function name from theccallit wraps, so the generated wrappers need no regeneration, and a successful call runs exactly as before.