/explore
|
You are here 
|
cullmann.io | ||
| | | | |
hackingcpp.com
|
|
| | | | | A list of the major C++ compilers in 2023. | |
| | | | |
github.com
|
|
| | | | | MSVC's implementation of the C++ Standard Library. - STL/stl/inc/vector at 530bdc5aaa8a21277e1281ad3df8b8d8433b5caa · microsoft/STL | |
| | | | |
s0rcy.github.io
|
|
| | | | | A few months ago while assessing the extensions API for a client, I got tasked with doing some light fuzzing against the application. The application allowed for third-party scripts to be executed in the parent application. I decided to use libFuzzer as a base, as it felt appropriate for the project. The client's code was simple to compile and writing the harness turned out to be easy, but I hit a bit of a problem; I had originally written the harness and buildscript on a macOS laptop using llvm/clang, and my client usually built with MSVC and wanted to run the fuzzer on Windows hosts. Thankfully libFuzzer supports both platforms, so that should be easy, right? | |
| | | | |
fnordig.de
|
|
| | | Personal website of Jan-Erik Rediger | ||
