On 28 Feb 2011, at 5:39pm, Mickey Mestel wrote: > dan, >> >> I've have never tried this. But if I had the problem above, I would. >> >> http://landonf.bikemonkey.org/code/iphone/iPhone_Simulator_Valgrind.20081224.html > > looks interesting, but it doesn't support arm, which is where the > problem is showing up.
The theory is that you are actually doing something wrong in your code, and this triggers obvious problems on the iPhone itself because the iPhone itself is so tight on space. However the simulator doesn't uncover these problems because it has plenty of memory and stack space: busting the stack never makes it run into the space used for normal memory because they're so far apart. The idea of valgrind is to be completely paranoid about the execution environment, spotting cases where things change when the instruction that was just executed shouldn't change them, making sure the heap changes only one item at a time, etc.. Running this on the simulator may make it as sensitive to bad code as the iPhone itself. I'm not saying it'll definitely spot your problem, but it may help. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
