- Original Message -
On Sunday, June 03, 2012, Paul Floyd wrote:
I'll try adding it and confirm either tonight or tomorrow.
Please do.
Hi
Just done the test, and the problem is fixed.
A+
Paul
--
Live
On 04/06/12 12:27, Christoph Bartoschek wrote:
how should one interpret the following report:
Thread #11: Bug in libpthread: recursive write lock granted on
mutex/wrlock which does not support recursion
==00:13:17:12.428 20623==at 0x4C2D18D: pthread_spin_lock (in
Am 04.06.2012 14:00, schrieb Tom Hughes:
On 04/06/12 12:27, Christoph Bartoschek wrote:
how should one interpret the following report:
Thread #11: Bug in libpthread: recursive write lock granted on
mutex/wrlock which does not support recursion
==00:13:17:12.428 20623==at 0x4C2D18D:
On 6/4/2012 1:23 PM, Amstoutz Marc wrote:
Hi valgrind experts,
I’m facing an unhandled instruction issue when valgrinding ing intel-ipp
libraries.
~/valgrind-3.7.0/bin/valgrind --tool=memcheck --leak-check=full
--show-reachable=yes
--error-limit=no --log-file=valgrnd.txt
On Mon, 2012-06-04 at 14:14 +0200, Christoph Bartoschek wrote:
Am 04.06.2012 14:00, schrieb Tom Hughes:
On 04/06/12 12:27, Christoph Bartoschek wrote:
how should one interpret the following report:
Thread #11: Bug in libpthread: recursive write lock granted on
mutex/wrlock which does
On Monday, June 04, 2012, Eliot Moss wrote:
unhandled here). A quick look suggests that this is a PADDB instruction.
Yes, 64-bit (MMX) PADDB. Problem is it has a redundant REX prefix
(IPP is very strong on those, for some reason), and Valgrind pretty
much rejects all redundant REX prefixes.
