Английская Википедия:Insure++

Материал из Онлайн справочника
Версия от 07:42, 26 марта 2024; EducationBot (обсуждение | вклад) (Новая страница: «{{Английская Википедия/Панель перехода}} {{Short description|Memory debugger software}} {{Infobox software | name = Insure++ | logo = Parasoft Logo 2017.png | screenshot = | caption = | collapsible = | developer = Parasoft | released = {{Start date and age|1993}} | latest_release_version = 2021.2 | latest_release_date = {{release date|2021|10|28}} | operating_system = Cross-platform, Linux, Solaris (operating...»)
(разн.) ← Предыдущая версия | Текущая версия (разн.) | Следующая версия → (разн.)
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Infobox software

Insure++ is a memory debugger computer program, used by software developers to detect various errors in programs written in C and C++. It is made by Parasoft, and is functionally similar to other memory debuggers, such as Purify, Valgrind and Dr Memory.[1]

Overview

Insure++ can automatically find erroneous accesses to freed memory (use-after-free situations), array-bounds violations, freeing unallocated memory (which often happens when a programmer frees the same memory twice, or when he frees global or stack memory), and many others.[2]

Unlike Purify and Valgrind, Insure++ inserts its instrumentation at the source-code level,[3][4]Шаблон:Clarify which allows it to detect errors that the other tools miss.[5] In particular, Insure++ can detect buffer overflows in automatic arrays, and overflows which involve pointers that accidentally "jump" from one valid memory region to another, as in the following example:

#include <stdlib.h>
int main()
 {
    char *p = malloc(1024); /* first dynamically-allocated block */
    char *q = malloc(1024); /* second block */
    p += 1200; /* At this point, "p" is likely to point into the second block. 
                  However, false assumptions about the real behaviour lead to mistakes. */
    *p = 'a';  /* invalid write (past the end of the first block) */
 }

The source-level instrumentation allows it to not only identify that a leak occurred, but where it occurred.[1] Some tools merely provide information about where the memory was allocated, Insure++ also gives a stack trace for when/where the actual leak occurred.

Additionally, Insure++ will produce Linear Code Sequence and Jump Code Coverage metrics for all tested code.

See also

References

Шаблон:Reflist

External links


Шаблон:Programming-software-stub