On Mon Mar 10 21:27:56 2014, public@khwilliamson.com wrote: > Better than nothing is to add a comment at the place where a future > investigator is likely to go first. I thought about doing that, but the problem is the error backtraces point outside of where the problem is actually occurring. The only real solutions I see: 1) zero the memory before calling semctl() This may lead to a different false-negative for valgrind - if the semctl() fails, valgrind will treat the memory as initialized, even though it's not initialized usefully. 2) use test script specific suppressions They need to be script specific since, at least for this case the error is occurring in code that has nothing to do with semctl(), suppressing this call stack globally could lead to suppressing other unrelated errors. Tony --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=121335