https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #42 from Mark Wielaard <m...@klomp.org> --- drd/tests/condvar fails with Other thread: waiting for notify Other thread: notified RISCV64 front end: standard disInstr(riscv64): unhandled instruction 0x8330000F disInstr(riscv64): 1000'0011 0011'0000 0000'0000 0000'1111 ==1493609== valgrind: Unrecognised instruction at address 0x10bbda. ==1493609== at 0x10BBDA: std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>::_M_release_last_use() (shared_ptr_base.h:182) ==1493609== by 0x10ADBF: std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>::_M_release() (shared_ptr_base.h:311) ==1493609== by 0x10BCAD: std::__shared_count<(__gnu_cxx::_Lock_policy)1>::~__shared_count() (shared_ptr_base.h:1071) ==1493609== by 0x10B855: std::__shared_ptr<std::__future_base::_State_baseV2, (__gnu_cxx::_Lock_policy)1>::~__shared_ptr() (shared_ptr_base.h:1524) ==1493609== by 0x10B875: std::shared_ptr<std::__future_base::_State_baseV2>::~shared_ptr() (shared_ptr.h:175) ==1493609== by 0x10B895: std::__basic_future<void>::~__basic_future() (future:695) ==1493609== by 0x10B8DD: std::future<void>::~future() (future:878) ==1493609== by 0x10A8E1: main (condvar.cpp:55) ==1493609== Your program just tried to execute an instruction that Valgrind ==1493609== did not recognise. There are two possible reasons for this. ==1493609== 1. Your program has a bug and erroneously jumped to a non-code ==1493609== location. If you are running Memcheck and you just saw a ==1493609== warning about a bad jump, it's probably your program's fault. ==1493609== 2. The instruction is legitimate but Valgrind doesn't handle it, ==1493609== i.e. it's Valgrind's fault. If you think this is the case or ==1493609== you are not sure, please let us know and we'll try to fix it. ==1493609== Either way, Valgrind will now raise a SIGILL signal which will ==1493609== probably kill your program. This seems to be: __atomic_thread_fence (__ATOMIC_ACQ_REL); => 0x000000000010bbda <+28>: fence.tso -- You are receiving this mail because: You are watching all bug changes.
