GNU Astronomy Utilities - Tasks: task #16379, Handling errors in Gnuastro...
You are not allowed to post comments on this tracker with your current authentication level.
task #16379: Handling errors in Gnuastro Dependencies.
Submitter: | Labib Asari <labeeb7z> | ||
Submitted: | Tue 13 Jun 2023 03:25:52 PM UTC | ||
Should Start On: | Tue 13 Jun 2023 12:00:00 AM UTC | Should be Finished on: | Tue 13 Jun 2023 12:00:00 AM UTC |
Category: | Development | Priority: | 5 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Percent Complete: | 0% | Open/Closed: | Open |
Effort: | 0.00 |
Wed 14 Jun 2023 02:28:58 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Tue 13 Jun 2023 03:25:52 PM UTC, original submission:
The error handling mechanism of Gnuastro is being updated to remove the error(EXIT_FAILURE...) and store and report all the errors. This makes sure the program does not abort whenever an error occurs.
the GSL library crashes and aborts with the error message :
|
Labib Asari <labeeb7z> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-caa5.
Corresponding source code
Thanks for raising this point Labib.
For completeness, here is how you can reproduce this problem on the command-line:
All Gnuastro dependencies have error-handling features. For example, here is the description in GSL. We should definitely account the errors in our dependencies while defining/completing Gnuastro's error reporting features.