wok-current annotate electric-fence/description.txt @ rev 25581
Up glibc 2.21
| author | Stanislas Leduc <shann@slitaz.org> |
|---|---|
| date | Wed May 17 06:35:38 2023 +0000 (21 months ago) |
| parents | |
| children |
| rev | line source |
|---|---|
| Hans-G?nter@24512 | 1 Electric Fence is a debugger that uses virtual memory hardware to detect illegal |
| Hans-G?nter@24512 | 2 memory accesses. |
| Hans-G?nter@24512 | 3 It can detect two common programming bugs: |
| Hans-G?nter@24512 | 4 software that overruns or underruns the boundaries of a malloc() memory allocation, |
| Hans-G?nter@24512 | 5 and software that touches a memory allocation that has been released by free(). |
| Hans-G?nter@24512 | 6 |
| Hans-G?nter@24512 | 7 Unlike other malloc() debuggers, Electric Fence will detect read accesses as well |
| Hans-G?nter@24512 | 8 as writes, and it will stop and pinpoint the exact instruction that causes an error. |
| Hans-G?nter@24512 | 9 It is not as thorough as Purify, however. |
| Hans-G?nter@24512 | 10 |
| Hans-G?nter@24512 | 11 In order to debug a program it needs to be linked with Electric Fence's library or |
| Hans-G?nter@24512 | 12 dynamic linking needs to be used. |