Hi, On Nov 29, 2010, at 4:24 PM, Antonio Borneo wrote:
>> I did some more poking. Maybe it will be useful. As this seems to be a >> memory problem I thought maybe electric-fence will tell us something useful. >> So I compiled oocd with libefence, and this is what I get: >> > Try also "valgrind". > My understanding on electric-fence is that it uses MMU to set page > access permission. This method cannot set anything smaller that the > page size. > So, if you malloc a buffer of 1 byte, you get a full page with R/W permission. > Valgrind, instead, is a x86 (or PPC on old MAC) simulator. It catch > every memory access outside the range return by malloc. > > Antonio Thanks will try that next. I also dissected the commits and found out that the bug got introduced with commit: 3b68a708c2b039d9b091608eccb2206725742a47 ADIv5: remove ATOMIC/COMPOSITE interface mode In the previous revision everything works and with this one it stops working for me. Cheers Esden -- Blog: http://www.esden.net Projects: http://open-bldc.org http://paparazziuav.org http://github.org/esden/floss-jtag http://github.org/esden/summon-arm-toolchain
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
