On Mon, Dec 13, 2010 at 21:17, Steve Bennett <[email protected]> wrote: > On 14/12/2010, at 5:50 AM, Domen Puncer wrote: > >> On Mon, Dec 13, 2010 at 20:32, Steve Bennett <[email protected]> wrote: >>> On 13/12/2010, at 11:00 PM, Domen Puncer wrote: >>> >>>> On Mon, Dec 13, 2010 at 12:47, Steve Bennett <[email protected]> >>>> wrote: >>>>> >>>>> Can we see the code being evaluated here? >>>>>> ==32465== by 0x4B6DB2: Jim_Eval_Named (jim.c:9644) >>>>> >>>> >>>> 9643 else { >>>> 9644 retval = Jim_EvalObj(interp, scriptObjPtr); >>>> 9645 } >>>> 9646 Jim_DecrRefCount(interp, scriptObjPtr); >>>> 9647 return retval; >>>> 9648 } >>> >>> Sorry, I meant the Tcl script that is being evaluated at that point. >> >> Oh, I don't know. >> How do I find out? >> It was after "verify_image" and "reset init" commands executed with >> too high clock (so there were some errors printed, as mentioned in >> original post). > > Never mind. I see this in target.c: > > sprintf(buf, "ocd_process_reset %s", n->name); > retval = Jim_Eval(cmd_ctx->interp, buf); > > So it is executing a pretty simple script. > > Is there any chance you can build just jim.c with '-g -O0' and rerun with > valgrind?
I tried that before, well... actually only '-g', valgrind reported no problems. It's a tricky one, isn't it :-) -- Domen _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
