Skip to content

Not handling preCICE exceptions #362

Open
@MakisH

Description

@MakisH

Since preCICE v3.2.0, preCICE has more refined error handling via exceptions. However, these might give a very bad impression to the user, if not handled correctly, as the (often very clear) error message is accompanied by a stack trace that is not relevant for the user (and for this reason, I am adding the bug label here).

Example:

wild-exception.txt

We should wrap the calls to the preCICE API with exception handlers. Example (by @fsimonis in the developers chat):

void myfunction() 
try {
  // boom code
} except (precice::Error& e) {
  // make error digestible for solver user
  std::exit(1);
}

This would be a backwards-compatible change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUnexpected problems (crashes, numerical issues, etc)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions