|
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6, llvmorg-19.1.5, llvmorg-19.1.4, llvmorg-19.1.3 |
|
| #
29097dd2 |
| 17-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan][NFC] Remove rtsan_ prefix from stats variables (#112762)
|
| #
8f8d5f00 |
| 17-Oct-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Add statistics for suppression count (#112718)
|
|
Revision tags: llvmorg-19.1.2, llvmorg-19.1.1 |
|
| #
f5b95db4 |
| 26-Sep-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Only print out unique stack traces (#110028)
# Why?
In real-time programming, you often have a process or dispatch loop that
is called many, many, many times. Without de-duplication the
[rtsan] Only print out unique stack traces (#110028)
# Why?
In real-time programming, you often have a process or dispatch loop that
is called many, many, many times. Without de-duplication the user will
be drowning in errors.
Introduce a way to only print the stacks one time only, if they have
been seen before
show more ...
|
| #
c3334dad |
| 25-Sep-2024 |
Chris Apple <cja-private@pm.me> |
[rtsan] Add exit statistics (#109885)
adds the flag `print_stats_on_exit` which mirrors nsan's same flag.
# Why?
Not only is this nice for the end users, this gives us a very trivial
way to t
[rtsan] Add exit statistics (#109885)
adds the flag `print_stats_on_exit` which mirrors nsan's same flag.
# Why?
Not only is this nice for the end users, this gives us a very trivial
way to test deduplication which is next up
Currently the style is something like:
```
RealtimeSanitizer exit stats:
Total error count: 488
```
show more ...
|