[Bug 1052] Seg Fault in realtime logging with several components
Christian Fuchs <[email protected]> Thu, 23 Jan 2014 09:13:54 +0100
| Newsgroups | gmane.science.robotics.orocos.devel |
|---|---|
| Message-ID | <[email protected]> |
http://bugs.orocos.org/show_bug.cgi?id=1052 --- Comment #1 from Christian Fuchs <[email protected]> 2014-01-23 09:13:52 CET --- The issue is caused by a race condition in the OCL::logging::Category's OutputPort logging the last written message. The access to this variable is not threadsafe, leading to the old value being free'd more than once, when two or more threads use the same category to log a message concurrently. A workaround is to set the OutputPort's default behaviour to not logging the last written value. -- Configure bugmail: http://bugs.orocos.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug. -- Orocos-Dev mailing list [email protected] http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev