googol-lab
diff --git a/‎02-Use_the_Tools_Available.md
Lines changed: 19 additions & 15 deletions b/‎02-Use_the_Tools_Available.md
Lines changed: 19 additions & 15 deletions
@@ -32,7 +32,7 @@ Use an industry standard widely accepted build tool. This prevents you from rein
  * [maiken](https://github.com/Dekken/maiken) - Crossplatform build tool with Maven-esque configuration style.
  * [Qt Build Suite](http://doc.qt.io/qbs/) - Crossplatform build tool From Qt.
  * [meson](http://mesonbuild.com/index.html) - Open source build system meant to be both extremely fast, and, even more importantly, as user friendly as possible.
- * [premake](https://premake.github.io/) 
+ * [premake](https://premake.github.io/)
 
 
 Remember, it's not just a build tool, it's also a programming language. Try to maintain good clean build scripts and follow the recommended practices for the tool you are using.
@@ -66,7 +66,7 @@ Continuous Integration (CI) tools automatically build the source code as changes
    * Java Application Server is required
    * supports Windows, OS X, and Linux
    * extendable with a lot of plugins
- * [TeamCity](https://www.jetbrains.com/teamcity) 
+ * [TeamCity](https://www.jetbrains.com/teamcity)
    * has a free option for open source projects
  * [Decent CI](https://github.com/lefticus/decent_ci)
    * simple ad-hoc continuous integration that posts results to GitHub
@@ -88,7 +88,7 @@ If you have an open source, publicly-hosted project on GitHub:
  * go enable Travis Ci and AppVeyor integration right now. We'll wait for you to come back. For a simple example of how to enable it for your C++ CMake-based application, see here: https://github.com/ChaiScript/ChaiScript/blob/master/.travis.yml
  * enable one of the coverage tools listed below (Codecov or Coveralls)
  * enable [Coverity Scan](https://scan.coverity.com)
-  
+
 These tools are all free and relatively easy to set up. Once they are set up you are getting continuous building, testing, analysis and reporting of your project. For free.
 
 
@@ -121,7 +121,7 @@ You should use as many compilers as you can for your platform(s). Each compiler
  * `-Wdouble-promotion` (GCC >= 4.6, Clang >= 3.8) warn if `float` is implicit promoted to `double`
  * `-Wformat=2` warn on security issues around functions that format output (ie `printf`)
  * `-Wlifetime` (only special branch of Clang currently) shows object lifetime issues
- 
+
 Consider using `-Weverything` and disabling the few warnings you need to on Clang
 
 
@@ -187,7 +187,7 @@ CMake now also comes with built-in support for calling `clang-tidy` during [norm
 
 The best bet is the static analyzer that you can run as part of your automated build system. Cppcheck and clang meet that requirement for free options.
 
-### Coverity Scan 
+### Coverity Scan
 
 [Coverity](https://scan.coverity.com/) has a free (for open source) static analysis toolkit that can work on every commit in integration with [Travis CI](http://travis-ci.org) and [AppVeyor](http://www.appveyor.com/).
 
@@ -201,16 +201,16 @@ The best bet is the static analyzer that you can run as part of your automated b
 Notes:
 
  * For correct work it requires well formed path for headers, so before usage don't forget to pass: `--check-config`.
- * Finding unused headers does not work with `-j` more than 1. 
+ * Finding unused headers does not work with `-j` more than 1.
  * Remember to add `--force` for code with a lot number of `#ifdef` if you need check all of them.
- 
+
 ### cppclean
 
 [cppclean](https://github.com/myint/cppclean) - Open source static analyzer focused on finding problems in C++ source that slow development of large code bases.
 
- 
+
 ### CppDepend
- 
+
 [CppDepend](https://www.cppdepend.com/) Simplifies managing a complex C/C++ code base by analyzing and visualizing code dependencies, by defining design rules, by doing impact analysis, and comparing different versions of the code. It's free for OSS contributors.
 
 ### Clang's Static Analyzer
@@ -237,7 +237,7 @@ Can be enabled with the `/analyze` [command line option](http://msdn.microsoft.c
 
 Both of these tools from [JetBrains](https://www.jetbrains.com/cpp/) offer some level of static analysis and automated fixes for common things that can be done better. They have options available for free licenses for open source project leaders.
 
-### Cevelop 
+### Cevelop
 
 The Eclipse based [Cevelop](https://www.cevelop.com/) IDE has various static analysis and refactoring / code fix tools available. For example, you can replace macros with C++ `constexprs`, refactor namespaces (extract/inline `using`, qualify name), and refactor your code to C++11's uniform initialization syntax. Cevelop is free to use.
 
@@ -267,7 +267,7 @@ A coverage analysis tool shall be run when tests are executed to make sure the e
    * integrates with Travis CI and AppVeyor
    * free for open source projects
  * [LCOV](http://ltp.sourceforge.net/coverage/lcov.php)
-   * very configurable 
+   * very configurable
  * [Gcovr](http://gcovr.com/)
  * [kcov](http://simonkagstrom.github.io/kcov/index.html)
    * integrates with codecov and coveralls
@@ -296,7 +296,7 @@ Be aware of the sanitizer options available, including runtime options. https://
 
 ### Fuzzy Analyzers
 
-If your project accepts user defined input, considering running a fuzzy input tester. 
+If your project accepts user defined input, considering running a fuzzy input tester.
 
 Both of these tools use coverage reporting to find new code execution paths and try to breed novel inputs for your code. They can find crashes, hangs, and inputs you didn't know were considered valid.
 
@@ -323,7 +323,7 @@ MSVC's [Control Flow Guard](https://msdn.microsoft.com/en-us/library/windows/des
 
 ### Heap Profiling
 
- * [https://epfl-vlsc.github.io/memoro/](Memoro) - A detailed heap profiler 
+ * [https://epfl-vlsc.github.io/memoro/](Memoro) - A detailed heap profiler
 
 ## Ignoring Warnings
 
@@ -373,18 +373,22 @@ Don't forget to make sure that your error handling is being tested and works pro
 
 [ABI Compliance Checker](http://ispras.linuxbase.org/index.php/ABI_compliance_checker) (ACC) can analyze two library versions and generates a detailed compatibility report regarding API and C++ ABI changes. This can help a library developer spot unintentional breaking changes to ensure backward compatibility.
 
-### CNCC 
+### CNCC
 
 [Customizable Naming Convention Checker](https://github.com/mapbox/cncc) can report on identifiers in your code that do not follow certain naming conventions.
 
 ### ClangFormat
 
 [ClangFormat](http://clang.llvm.org/docs/ClangFormat.html) can check and correct code formatting to match organizational conventions automatically. [Multipart series](https://engineering.mongodb.com/post/succeeding-with-clangformat-part-1-pitfalls-and-planning/) on utilizing clang-format.
 
-### SourceMeter 
+### SourceMeter
 
 [SourceMeter](https://www.sourcemeter.com/) offers a free version which provides many different metrics for your code and can also call into cppcheck.
 
 ### Bloaty McBloatface
 
 [Bloaty McBloatface](https://github.com/google/bloaty) is a binary size analyzer/profiler for unix-like platforms
+
+### pahole
+
+[pahole](https://linux.die.net/man/1/pahole) generates data on holes in the packing of data structures and classes in compiled code. It can also the size of structures and how they fit within the system's cache lines.