GNU Astronomy Utilities - Tasks: task #14258, Configure option to run tests with...
You are not allowed to post comments on this tracker with your current authentication level.
task #14258: Configure option to run tests with Valgrind
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Thu 01 Dec 2016 03:25:35 PM UTC | ||
Should Start On: | Thu 01 Dec 2016 03:00:00 PM UTC | Should be Finished on: | Thu 01 Dec 2016 03:00:00 PM UTC |
Category: | Development | Priority: | 5 - Normal |
Item Group: | Crash | Status: | Postponed |
Privacy: | Public | Assigned to: | None |
Percent Complete: | 90% | Open/Closed: | Open |
Effort: | 0.00 |
Wed 08 Aug 2018 09:20:07 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Thu 01 Dec 2016 03:25:35 PM UTC, original submission:
When a segmentation fault error (or similar opaque errors) are reported, it is really hard to find the cause of the problem on the user's system. The best way is use Valgrind, which gives a very nice report of exactly which function caused the memory failure.
|
Mohammad Akhlaghi <makhlaghi> |
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.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-08-08 | makhlaghi | Percent Complete | 0% | 90% |
Powered by Savane 3.13-02a9.
Corresponding source code
The basic premise of this task has been applied and pushed to the main repo.
However, the leak-check feature isn't added because it isn't critical to the failure of a test. Maybe later we can add another option (or a value to this option) so a more strict Valgrind test to be done with `--leak-check'.