Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Documentation: Add instructions for workaround for deadlysignal in un… #1366

Merged
merged 1 commit into from
Apr 22, 2024
Merged

Documentation: Add instructions for workaround for deadlysignal in un… #1366

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/development/unit_testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,16 @@ used in the unit tests as well. In some cases unit tests must be disabled based
if a particular file is not included in the build. A unit test file can be disabled based on configuration by using
an annotation like this:

## AddressSanitizer
If you are facing issues running the unit tests locally and ending up in an endless loop of

Addressanitizer:DEADLY SIGNAL

This is due to a incompatibility between TSan vesion and the high number of entropy bits used for randomization in recent Ubuntu versions.
Solutions for this (until a fix is in place) is to run the tests with the toolbelt or temporarily bump your systems entropy bits down to 28 using;

`sudo sysctl vm.mmap_rnd_bits=28`

``` c
// @IGNORE_IF_NOT CONFIG_DECK_LIGHTHOUSE
```
Loading