Am 05.06.2012 20:12, schrieb Christoph Bartoschek:
>>>
>>> How can this happen?
>>
>>
>> Was that output produced by Valgrind 3.7.0 ? If so, do you get the same
>> output if you build Valgrind from the SVN trunk ?
>
>
> Yes it was from 3.7.0. I start a run with SVN trunk. It takes about 20
> hours.
The first errors show up and I see the same problem. A race is reported
for memory that has just been allocated and is now filled.
Is it possible that DRD thinks that the memory still belongs to a
different allocation?
I see also another strange thing:
Other segment end (thread 7)
at 0x4C32042: pthread_spin_init (drd_pthread_intercepts.c:813)
by 0x7A4719: spin_np_t::unlock(legos::spin_np_t*) (legos_spin.C:117)
The line legos_spin.C:117 is:
int rc = pthread_spin_unlock( &s->_spin );
So why is DRD reporting pthread_spin_init?
Thanks
Christoph
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
