-
@CiosG commented in #690:
> When "unprocessed" patterns are stored Aztec stores both "processed" and "unprocessed" in project folders, there should be .ebsp and .uebsp files both have the same name…
-
Add a test that checks a simple integration tests works when Firecracker is instrumented with [src/clippy-tracing](https://github.com/firecracker-microvm/firecracker/tree/main/src/clippy-tracing) and …
-
Tested as of db1a76206902e6926464e30cc47249e217405dab, the last worked was with llvm-17
Repro:
```
$ export LDFLAGS="-Wl,-O1 -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=0x1000 -Wl,-Bsymbolic-fun…
-
```
#0 0x00000001083f0228 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/opt/llvm18/bin/lldb+0x100022228)
#1 0x00000001083ee40a llvm::sys::RunSignalHandlers() (/opt/llvm18/bin/lldb+0x100020…
-
Instrumentation I have been writing for x64 Windows binaries has been breaking on any complex program due to faulty indirect jumps, coming from broken switch jump tables or C++ jump tables.
I belie…
-
When dealing with code generated from templates it's easy to miss source files which need to be compiled with certain flags to make sure cross-compartment direct calls go through symbol versioning wra…
-
_From @GoogleCodeExporter on March 19, 2015 16:27_
```
What steps will reproduce the problem?
1. Compile any ReactOS module.
2. Try to ASAN instrument it by following the instructions in the wiki.
…
-
```
What steps will reproduce the problem?
1. Compile any ReactOS module.
2. Try to ASAN instrument it by following the instructions in the wiki.
What is the expected output? What do you see instead…
-
In my integration tests I am spawning my app via `Command` triggered `cargo run`.
When executing `cargo tarpaulin --follow-exec` I am getting some errors
```bash
2024-09-17T12:25:29.431195Z IN…
lcmgh updated
1 month ago
-
Currently, emscripten instruments wasm binaries without using `--in-memory` or `--in-secondary-memory` wasm-split options when threads are enabled [here](https://github.com/emscripten-core/emscripten/…