Hello,
We try to run valgrind on a Linux system (with kernel: 2.6.32.13). Although valgrind seems to work we get the bellow error (attached the complete log from valgrind)!
Does anyone had this issue before?
==18202== ERROR SUMMARY: 4 errors from 2 contexts (suppressed: 0 from 0)
==18202==
==18202== 2 errors in context 1 of 2:
==18202== Conditional jump or move depends on uninitialised value(s)
==18202== at 0x40026C4: ??? (in /lib/ld-2.11.1.so)
==18202== by 0x40168EF: ??? (in /lib/ld-2.11.1.so)
==18202== Uninitialised value was created by a stack allocation
==18202== at 0x400228C: ??? (in /lib/ld-2.11.1.so)
==18202==
==18202==
==18202== 2 errors in context 2 of 2:
==18202== Conditional jump or move depends on uninitialised value(s)
==18202== at 0x400268C: ??? (in /lib/ld-2.11.1.so)
==18202== by 0x40168EF: ??? (in /lib/ld-2.11.1.so)
==18202== Uninitialised value was created by a stack allocation
==18202== at 0x400228C: ??? (in /lib/ld-2.11.1.so)
==18202==
==18202== ERROR SUMMARY: 4 errors from 2 contexts (suppressed: 0 from 0)
Some info:
CPU: P1021
Linux kernel: 2.6.32.13
Valgrind version: Valgrind-3.7.0
Thank you in advance,
-George
Original Attachment has been moved to: valgrind_log.txt.zip
The full log shows also that an SPE instruction is not handled by valgrind.
The release of SDK 1.4 in June is planned to contain an update to valgrind resolving such issues.
Hi Heinz-
Does freescale have a patchset for this available now? I'd like to get valgrind working for the p10xx/p20xx procs.
Thanks!
Jason
Jason,
I would recommend to wait until 2nd half June for the SDK 1.4 release. It would be a resource distraction to pull out things today before they have gone through all testing and integration.
If you really, really, really, need something earlier then in ~3weeks I would suggest you open up a service request on the Freescale web. I am not promising that they will not also point to the SDK 1.4 release.
Best regards,
Heinz
Thanks for the quick response, Heinz. I'll go ahead and wait. Very eagerly.
Thanks!
Jason