kushmer@bnlux0.bnl.gov (christopher kushmerick) (01/10/91)
A while ago a posted that I was having trouble with F-4 (run to cursor), in the integrated debugger, TP6.0 Symptom: turbo would make the patently false assertion that no code was generated for the line that the cursor was on. Setting breakpoints there would result in a "invalid breakpoint" error. What was going on: Tp6.0 allows one to load many copies of the same source file at one time. Turbo picks one of these to be the "real" version, meaning the one that is actually compiled, assuming that there is a primary file specified and the command is Make. So, when you are in any version of the file except the "real" version, F-4 acts just as you would expect it to act if you were in any old text file. The trick will be to figure out which file is the "real" version. Presumable it is either A: easy to figure out, like the first version loaded, or B: in the manual. In A: above, one consideration is that when I exit, and then reenter, all of the files that were loaded when I exited are reloaded. So it is not necessarily easy to remember which window received the first version of the text file. This all came about because I accidently loaded the same file more than once. There should be a command to open a file only if it is not already open and in a different window. The way it is now, you have to remember whats already open, consequently you are required to concentrate on programming, while programming. -- Chris Kushmerick kushmer@bnlux0.bnl.gov <===Try this one first kushmerick@pofvax.sunysb.edu