before and after this variable which got overwritten create dummy variables and set them with some magic values (not zeros!)
then just check these values very often (maybe with some macro) and show alert/stop on breakpoint as soon as they got changed. when you will know area where it happens you can make check happen ore often and soon you will know exact line Luc Le Blanc wrote: > I ported a piece of mathematical C# code to MW C++ and at some point, a > perfectly legit API frm call causes a bus error. I suspect the error is > caused by some earlier memory overwrite in the ported classes. Are there > tricks to detect such overwrites or to test the integrity of the memory? > > > Luc Le Blanc > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
