|author||Tom Hacohen <email@example.com>||2016-09-22 13:16:18 +0100|
|committer||Tom Hacohen <firstname.lastname@example.org>||2016-09-22 13:59:46 +0100|
Eo: introducing libeo_dbg.so.
This has been in the making for a very long time. Thanks to Marcel for reminding me to do it. What is it? This is a tool to help application developers debug their apps with everything Eo. Eo is strict, but not as strict as it can be. Many strict tests and debug are very expensive to implement, and we have so many hot-paths that even basic "ifs" to check if debugging is enabled will add significant overhead to normal running applications. This is why I created this library. All the expensive tests and bookkeeping should be wrapped around with "#ifdef EO_DEBUG". With this change, libeo.so is compiled twice, once normally, and once with this define set (as libeo_dbg.so). This means that normal eo code will not be affected, but if you decide to debug your application, all you need to do is: LD_PRELOAD=/path/to/libeo_dbg.so ./app Or use the convenient wrapper: eo_debug ./app Which will load the debug heavy version. What's currently there: at the moment, EO_DEBUG enables xref and data_xref and stricter tests when fetching object data. In the future, I also plan introducing "zombie objects", which essentially mean that objects are never really deleted, so you can query them long after they are gone to get more information on what they were. So if for example you have an object id that you want to query after the object has been deleted, you can. I also plan on having a way to disable/enable certain debug mode features via env vars, and maybe make the test suite link against this one instead of the normal one, and possibly add more internal hooks for the test suite to better inspect internal state? P.S: The amount of errors spewed out when running it on elementary_test makes me wish I wrote this earlier. :( @feature
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions