We're updating the issue view to help you get more done. 

raspberrypi helgrind issue - with set<signals> - APPEARS false positive

Description

$ valgrind --gen-suppressions=yes -q --tool=helgrind --suppressions=Valgrind-Helgrind-Common.supp /tmp/Test37
Succeeded
==1293== ---Thread-Announcement------------------------------------------
==1293==
==1293== Thread #2 was created
==1293== at 0x495C8F8: clone (clone.S:58)
==1293==
==1293== ---Thread-Announcement------------------------------------------
==1293==
==1293== Thread #1 is the program's root thread
==1293==
==1293== ----------------------------------------------------------------
==1293==
==1293== Possible data race during read of size 4 at 0x4A4A4B4 by thread #2
==1293== Locks held: none
==1293== at 0x12EC98: Stroika::Foundation::Containers::Concrete::Set_stdset<int>::Rep_<std::less<int> >::~Rep_() (in /tmp/Test37)
==1293== Address 0x4a4a4b4 is 4 bytes inside a block of size 24 alloc'd
==1293== at 0x4840FE8: operator new(unsigned int) (vg_replace_malloc.c:328)
==1293== by 0x12E303: std::_Function_base::_Base_manager<Stroika::Foundation::Execution::SignalHandler>::_M_manager(std::_Any_data&, std::_Any_data const&, std::_Manager_operation) (in /tmp/Test37)
==1293== Block was alloc'd by thread #1
==1293==
==1293==

ONLY happens on raspberrypi (and only since I reinstalled OS).

For now just suppress and retry another time.

Marked MEDIUM priority ONLY because I had to use a suppression that is unformately going to match alot.

Environment

None

Status

Assignee

Lewis Pringle

Reporter

Lewis Pringle

Labels

None

Components

Priority

Low