[MXS-354] Memory Allocation Created: 2015-09-07 Updated: 2017-12-04 Resolved: 2016-10-17 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Epic Link: | Refactoring | ||||||||
| Description |
|
Currently the approach for dealing with memory allocation errors varies; some functions assume malloc and realloc can fail, others that they always will succeed, and most functions assume strdup will always succeed. The policy needs to be clearly defined and thereafter the usage throughout MaxScale must be modified to adhere to it. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-09-07 ] |
|
johan.wikman I think this should be a task rather then a story. |
| Comment by Johan Wikman [ 2015-09-07 ] |
|
I foresee that this will actually require several sub-tasks, but for now this is mostly a placeholder. |
| Comment by Dipti Joshi (Inactive) [ 2015-09-07 ] |
|
|