today i started working on a project i started a while back, i dropped it because i wasnt effeciant enough in c++. so anyway today im back workin on it and ive already sped it up considerable in the hour ive been tweakin and refining the code. but theres a problem, i get a bunch of First Chance Exceptions when i debug. i tried to find them by using the debug > exceptions settings (in the menu) to make it break on the exception, but it just shows the disassembly (Sp?) of one of the micorosft libs. my friend says its from trying to reference pointers (ie with ->) when they havent been initialized. that sounds like something i would have done back then because i wasnt all that clear on pointers (i am now . however im wondering if theres an easier way to find the errors other than single step the whole thing (as per his advice).. thanks -jeff Edited by - deadbeat on March 9, 2002 1:50:13 AM

Personally I dont use any advanced debugging techniques. I wish I knew how to use them because it would probably significantly increase my productivity I just read through my code until I find the mistake... I normally try to narrow it down by commenting out other code... Obviously this is -not- the best way to do things, by far! Just thought I''d post a little something though because noone else had



-------- E y e .Scream Software --------
----------------------------------------
                                  /-\
    http://www.eyescream.cjb.net | * |
                                  \-/
----------------------------------------