??? 06/01/07 12:24 Read: times |
#140148 - read the whole post Responding to: ???'s previous message |
Erik Malund said:
Optimization may combine the 'exit sequence' of two or more functions (been there seen that) and thus, if you want to breakpoint on the exit from one of these functions the breakpoint will break on the exit from ANY of the functions renedering the breakpoint useless. Erik, Andy said, "... does not affect the ability to set breakpoint...", and in the following sentences said exactly the same than you - that a breakpoint set in that way might be useless. There is a clear discrepancy between the aim of compiler (to provide the programmer abstraction from the hardware and machine instructions) and method how the standard debugging tools work (go down to hardware and machine instructions). Andy's point was (if I understand him correctly), that from the user's point of view, the breakpoint set for return from function A should break only if it IS a return from function A, no matter how far the optimised version is from the original source, and no matter how complicated that for the toolmakers is. Ideally, the user is DOES (SHOULD) NOT CARE of the troubles of the toolmaker in achieving this. JW |