On Nov 29, 2010, at 11:10 PM, Øyvind Harboe wrote: >> 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. > > Good catch! > > Unfortunately that's a pretty big commit. The next thing I could > suggest in terms of bisection would be to create a working > branch and split that commit as many times as possible and > do a bisect on that branch...
Allright, so I did that and applying the attached patch to revision ecff73 exposes the problem. But I have the feeling that it is not the core reason for this problem. This only exposes it. I think that it has something to do with memory corruption in openocd. The core dump appears in cortex_m3_assert_reset and the patch changes scan_inout_check_u32 that in my unknowing eyes does not seem to touch anything related to that. But I don't have enough insight in the openocd codebase. So maybe David who wrote the patch has some kind of an explanation to what is happening. Also if there are other Mac OS X users out there. It would be nice if they could try to compile the newest revision of openocd and see if they also get this kind of a crash to confirm that it has nothing to do with my setup? Because it is weird that the problem seems to be present since a while already and no one reported it until now. :) 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
patch-mac_os_crash_exposure.diff
Description: Binary data
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
