d697cdfca5
Context: https://help.github.com/articles/dealing-with-line-endings/ If you work on this repo on Windows, you quickly see the `.gitattributes` are not setup right for development on Windows. 1. Certain files had mixed line endings, which causes Visual Studio to prompt to adjust. 2. Running `premake` yields Windows line endings on Windows, and so every `*.csproj` file appears to have changes. `xamarin-android` has a well-used `.gitattributes` file, so I used it as a starting point and added an entry for `*.cake` files. The way it works (as I understand it): - `git` stores everything with unix line endings - on checkout, clients convert the line endings according to settings in the `.gitattributes` file So, for example: - All `*.csproj` files will have Windows line endings, as Visual Studio expects (both Mac and Windows) - `*.cs` files will have Windows line endings on Windows, and unix line endings on Mac |
||
|---|---|---|
| .. | ||
| Program.cs | ||
| README.md | ||
| leaktest.csproj | ||
README.md
This is a small wrapper around the command-line leaks tool that:
- Sets a few malloc variables before launching the executable that's to be tested.
- Launches the executable, requests it to wait before exiting (this needs
cooperation from the executable), and then launches
leakswhen the executable is at the end.
It also processes the output from leaks to make it more human readable.