C / C++ / MFC

position = tempInvestors->binarySearch(tempInvestors->getInvestorsList(),0,9,tempSS);
*tempInvestor = tempInvestors->getInvestor(position);
tempAB = tempInvestor->getAccountBalance(); //AccountBalance Of Buyer

// Here i'm performing another binary search to look for the 
// specific stock that has that same stockTicker
position = tempStocks->binarySearch(tempStocks->getMyStocks() , 0, 14, tempST);
*tempStock = tempStocks->getStock(position);//THIS LINE IS THE ERRONEOUS ONE
tempIV = tempStock->getInitialValue(); // storing the stockprice in tempStockPrice

:) Good boy, Marwan!

Nish :) 

a)Open your project in the VC++ editor.
<HR></HR>
b) Go to the file in which you have pasted the second piece of offending code 
i.e. this

position = tempInvestors->binarySearch(tempInvestors->getInvestorsList
(),0,9,tempSS);*tempInvestor = tempInvestors->getInvestor(position);tempAB = 
tempInvestor->getAccountBalance(); //AccountBalance Of Buyer// Here i'm 
performing another binary search to look for the // specific stock that has
 that same stockTickerposition = tempStocks->binarySearch(tempStocks-
>getMyStocks() , 0, 14, tempST);*tempStock = tempStocks->getStock
(position);//THIS LINE IS THE ERRONEOUS ONEtempIV = tempStock->getInitialValue
(); // storing the stockprice in tempStockPrice

<HR></HR>
c)Insert a Breakpoint on the first line of your seemingly offensive code. You 
do this by right clicking on the far left side of the line where you see the 
grey (grey color is the default) band (column). You will get a drop down list 
from which you select the first "Insert / Remove Breakpoint". Once it is 
clicked you will see a nice round filled (maroon by def) bullet in the column.
<HR></HR>
d)Make sure that you are building in debug mode.
<HR></HR>
e)Now press "F5" to start your debug session. You will go to VC++ IDE Debug 
mode and if your app has an GUI / console interface you will see it. 
Depending on whether this piece of offensive code (hereby referred to as OC) 
is called or you have to i/p something for it to be called you will either be 
seeing the OC with an arrow in the debugger(i.e. your proggie has been 
stopped there so that you can check the parameter values) or you will land in 
your program.:omg: 
<HR></HR>
f)If you land in your proggie while it's waitin for your i/p then i/p 
something so that the OC line 1 is called.
<HR></HR>
g)Now if you see the arrow (yellow by def) use the following key to execute 
your program step by step.
 "F10" to step over OC line num one
 "F11" to step into the "binarysearch" member function after which you can use  "F10"
<HR></HR>
h)Remember that whichever key you press watch for the consequences down in 
the Auto Watch variables window in which you will see your relevant auto variables. To check any other variables, Type them(name) in the 
Watchn window. After every step you execute of your proggie check for 
any logic,pointer discrepancies.
<HR></HR>
i)If while this stepping your proggie crashes you will nail the OC. If luck 
favors you it will be that same line otherwise check a few lines of code 
before that OC line.
<HR></HR>
j)If you want to stop debugging press Shift+F5

ftp://ftp.gammon.com.au/pennmush/unix2dos.zip - program to convert unix text files to DOS format 
ftp://ftp.gammon.com.au/pennmush/dos2unix.zip - program to convert DOS text files to Unix format 
ftp://ftp.gammon.com.au/pennmush/mac2unix.zip - program to convert Macintosh text files to Unix format 
ftp://ftp.gammon.com.au/pennmush/unix2mac.zip - program to convert Unix text files to Macintosh format 
ftp://ftp.gammon.com.au/pennmush/unix2dos.c - source code used to compile above 4 conversion programs