Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full stack error propagation #37

Closed
5 tasks done
ezorita opened this issue May 18, 2018 · 0 comments
Closed
5 tasks done

Full stack error propagation #37

ezorita opened this issue May 18, 2018 · 0 comments
Assignees
Milestone

Comments

@ezorita
Copy link
Owner

ezorita commented May 18, 2018

Description

Propagate errors in the code so that when the program crashes, the full stack of function calls is printed with a (optional) description message.

Subtasks

  • Define error macros.
  • Unify failure_return tags.
  • Update current code.

Acceptance criteria

  • All errors can be tracked.
  • All internal calls between library functions have error check and propagation.

Test procedures

It's difficult to unit test error propagation. A possibility is to check that the correct amount of lines (call stack) are written to stderr.

@ezorita ezorita added this to the Sprint 1 milestone May 18, 2018
@ghost ghost assigned ezorita May 18, 2018
ezorita added a commit that referenced this issue May 18, 2018
ezorita added a commit that referenced this issue May 18, 2018
@ezorita ezorita mentioned this issue May 22, 2018
This was referenced May 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant