xartigas pushed a commit to branch master. http://git.enlightenment.org/website/www-content.git/commit/?id=05816ed2fdc4bb6257249d912d0ddf395f6c83ea
commit 05816ed2fdc4bb6257249d912d0ddf395f6c83ea Author: Xavi Artigas <[email protected]> Date: Thu Apr 2 14:00:57 2020 +0200 Fix some typos in efl-debug, ASAN section. --- pages/contrib/efl-debug.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/pages/contrib/efl-debug.txt b/pages/contrib/efl-debug.txt index de6e3e011..dce43f542 100644 --- a/pages/contrib/efl-debug.txt +++ b/pages/contrib/efl-debug.txt @@ -296,18 +296,18 @@ In general it's a good idea to spend some quality time with GDB and do all this. === Asan === This is almost as good as Valgrind below, but drastically faster. -It's atually usable to build thing with Asan enabled and use them all -day long. You'll probably find it ueses about 2-3x the CPU and seems to +It's actually usable to build things with Asan enabled and use them all +day long. You'll probably find it uses about 2-3x the CPU and seems to use a lot of RAM (virtual size will be huge but overall footprint will be fine if you have *Gb or more of RAM). For a decently powerful desktop you should be able to use this as a daily driver especially when you are hunting bugs. Asan would definitely be the preferred deep-debugging -method and you should build at least EFL and the apps) (Enlightenment, +method and you should build at least EFL and the apps (Enlightenment, Terminology etc.) with Asan enabled to make it work correctly. To use Asan you will need to compile libraries and binaries with it -enabled and have a compiler capable of asan. Given the move to meson, -this is quite easy now. You will need this in your environmnet before +enabled and have a compiler capable of Asan. Given the move to meson, +this is quite easy now. You will need this in your environment before you compile and for when you run the application (it needs to be set before the process executes): @@ -332,14 +332,14 @@ meson -Db_sanitize=address [other meson options here] . build </code> So just add -Db_sanitize=address as an option in addition to any other -options you may pass and that build will enable asan for what is being +options you may pass and that build will enable Asan for what is being built. What this does is instruct the compiler to add extra checking -code when compiling that does much of what valgrind does at runtime. +code when compiling that does much of what Valgrind does at runtime. The added instructions generated by the compiler sanitize addresses before they are used and adds pointer tracking logic as well. That's why this needs to be done at compile time, but since it is done at compile time, the resulting binaries are relatively fast (compared to -using valgrind). +using Valgrind). Once you did the above just compile as normal: --
