Ángel

@angel@triptico.com



No twitter / no facebook / no instagram / no tiktok / no bluesky / no regrets

LA ATALAYA RECORTADA CONTRA EL CIELO (novela)https://librosdelfuturo.es/producto/la-atalaya-recortada-contra-el-cielo/
YO NO SOY PAVEL (novela)https://distrito93.com/catalogo/yo-no-soy-pavel/
wwwhttps://triptico.com
tilde.clubhttps://tilde.club/~angel/
Ann Hell Musichttps://exode.me/accounts/annhell
Keyoxidehttps://keyoxide.org/hkp/1AFAE6809099EB5CD65A4E32B498DDC28F4584FF

Location: 40.4235492,-3.6617828

99 following, 113 followers

0 ★ 1 ↺

[?]Ángel »
@angel@triptico.com

If you develop in C, you'll probably end up using memory leak detection tools like valgrind, libleak or the scan-build tool from the LLVM compiler. There is a less known tool inside the GCC compiler itself: the -fsanitize=address.

If you use a standard make setup, you can recompile your project doing

make CFLAGS="-fsanitize=address -fno-omit-frame-pointer"
After exiting your program, a summary of memory leak errors (including the line of the source code were it happened) will be printed out.