|
|
## Debug options
|
|
|
|
|
|
If you are using our library can be usefull, to put the library in debug mode to discover mamory corruption, overflow, memory leak, or any other abuse of API or bug in your code. The options are activated
|
|
|
in different ways if you are compiling the unit test or you are compiling external code
|
|
|
|
|
|
### External code
|
|
|
|
|
|
* defining the macro SE_CLASS1 before include any openfpm header enable security enhancements of class1
|
|
|
* define the macro SE_CLASS2 before include any openfpm header enable security enhancements of class2
|
|
|
* define the macro SE_CLASS3 before include any openfpm header enable security enhancements of class3
|
|
|
* define the macro
|
|
|
|
|
|
### Unit test
|
|
|
|
|
|
OpenFPM is in general is only header library with few exceptions, to compile the unit tests there are 4 that can be considered the most important options, in the install script these option are passed with -c "--enable-se-class1 --enable-se-class2 --enable-se-class3 --enable-debug"
|
|
|
|
|
|
* --enable-debug this option disable the optimizer and include debug information in the executables
|
... | ... | @@ -7,9 +19,3 @@ OpenFPM is in general is only header library with few exceptions, to compile the |
|
|
*
|
|
|
*
|
|
|
* --with-action-on-error |
|
|
|
|
|
In case the code that you are compiling is external the options are translated in
|
|
|
|
|
|
* define the macro SE_CLASS1 before include any openfpm file
|
|
|
* define the macro SE_CLASS2 before include any openfpm file
|
|
|
* define the macro SE_CLASS3 before include any openfom file |
|
|
\ No newline at end of file |