fjo@ttrdf.UUCP (Frank Owen ) (09/14/88)
in article <5154@fluke.COM>, mce@tc.fluke.COM (Brian McElhinney) says: > > ... but you can't > get to the complete stack frame. You cannot look at the related parameters, > or local variables, for that line of code (that's what I meant by stack frame; > the PC is only one part of it). > Yes. The above feature is VERY useful. The debugger I use here at work (not related to Mac development) has this capability, and life without it would be very tedious. This would be a welcome enhancement to the LSC debugger. (I'm not sure, but I think you can do something like this with the CodeView debugger in the MS-DOS world.). Another useful feature would be to allow the ability to place breakpoints not only at descrete statements, but somewhere in the middle of a statement. For example, in the following code: if( (foo(something) < anotherthing) || (bar(nothing) == junk)) { do_something(); } you can only place the breakpoint at the if statement. It is sometimes helpful to be able to place a breakpoint in the middle of the statement, like perhaps after the return from the call to "bar()". The other thing that would be nice would be to have a breakpoint that has some other effect than just halting the program and trapping to the debugger. You may want to set a breakpoint that when hit causes some variable to be set to some value, or perhaps enables another breakpoint and THEN resumes execution. This can be done manually with the current debugger, but having it done automatically helps. > Another feature I would love to see implemented is known in the UNIX world as > tags (the ctags program). It would allow you to, say, double click on a > symbol and be taken to it's definition in the source code. I think LSC has something like this. If you option-double-click on an instance of a variable, or subroutine call, the file that defined the symbol will be opened, and a "find" of the symbol will be made. This is often times NOT the definition of the symbol, but at least you have the correct file opened, and you can hit "command-A" to find again. -- Frank Owen (fjo@ttrdf) 312-982-2182 AT&T Information Systems Computer Systems Division, 5555 Touhy Ave., Skokie, IL 60077 PATH: ...!att!ttrdf!fjo