|
Mantis - ALGLIB
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 941 | General | minor | have not tried | 2022-05-21 22:10 | 2022-05-21 22:10 |
|
|
|||||
| Reporter: | SergeyB | Platform: | |||
| Assigned To: | SergeyB | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | resolved | Product Version: | |||
| Product Build: | Resolution: | implemented | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.19.0 | ||
| Programming language: | Unspecified | ||||
|
|
|||||
| Summary: | 0000941: IMPLEMENTED: red zones for C++ version | ||||
| Description: |
Red Zone is a fixed size area added before and after each dynamically allocated block. Red Zone is filled by the special red zone control value during its allocation. When the dynamically allocated block is freed, its control value is checked. Any change means that someone (either ALGLIB or user code that works with ALGLIB-allocated arrays) performed an out-of-bounds write. Red Zones are essential for finding memory access errors that silently corrupt your data and/or crash your program. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
|
|
|||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2022-05-21 22:10 | SergeyB | New Issue | |||
| 2022-05-21 22:10 | SergeyB | Status | new => assigned | ||
| 2022-05-21 22:10 | SergeyB | Assigned To | => SergeyB | ||
| 2022-05-21 22:10 | SergeyB | Programming language | => Unspecified | ||
| 2022-05-21 22:10 | SergeyB | Status | assigned => resolved | ||
| 2022-05-21 22:10 | SergeyB | Fixed in Version | => 3.19.0 | ||
| 2022-05-21 22:10 | SergeyB | Resolution | open => implemented | ||
| There are no notes attached to this issue. |