devilhorns pushed a commit to branch master. http://git.enlightenment.org/website/www-content.git/commit/?id=ba9f0f007f91214cfcf60c29e1a16e3a613ea0a1
commit ba9f0f007f91214cfcf60c29e1a16e3a613ea0a1 Author: Christopher Michael <[email protected]> Date: Wed Apr 1 09:29:02 2020 -0400 efl debug: Fix some minor typos, etc in recently added Asan section While reading a recent commit on this page, from a one armed man ;) , I noticed some minor typos, crazy question marks where they should not be, etc, etc ... so I used my two good hands ;) to fix the issues :) --- pages/contrib/efl-debug.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pages/contrib/efl-debug.txt b/pages/contrib/efl-debug.txt index b7e637758..de6e3e011 100644 --- a/pages/contrib/efl-debug.txt +++ b/pages/contrib/efl-debug.txt @@ -301,8 +301,8 @@ day long. You'll probably find it ueses 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. As an would definitely be the preferred deep-debugging -method and you should build at least EFL and the app9s) (Enlightenment, +hunting bugs. Asan would definitely be the preferred deep-debugging +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 @@ -312,7 +312,7 @@ you compile and for when you run the application (it needs to be set before the process executes): <code bash> -export ASAN_OPTIONS=detect_leaks=0:abort_on_error=1::new_delete_type_mismatch=0 +export ASAN_OPTIONS=detect_leaks=0:abort_on_error=1:new_delete_type_mismatch=0 </code> Ensure this is also in your ~/.xinitrc or ~/.xsession or otherwise @@ -321,7 +321,7 @@ interested in invalid memory accesses (e.g. use after free or out-of-bounds accesses etc.). Leaks are a different matter and not going to generally be a fatal issue we need Asan to go find. -When youcompile EFL or Enlightenment or Terminology or anything using +When you compile EFL or Enlightenment or Terminology or anything using meson add the following option when configuring meson (-Db_sanitize=address) and ensure we don't optimize the code so we get proper backtraces and symbols and have GDB debugging enabled: @@ -351,9 +351,9 @@ ninja -C build install Note that with Asan, debugging any app is just like using gdb but with the added extra that Asan will spew out some debug information and traces to stderr before aborting (which can be caught in GDB as -normal). Ylou canuse GD?b to poke around the variables and backtrace +normal). You can use GDB to poke around the variables and backtrace to see what happened just with the added benefit of the address -mis-use benig caught immediately and not indirectly "some time later +misuse being caught immediately and not indirectly "some time later after the bug actually happened many hundreds, thousands or millions of instructions before". --
