On 25/10/2010 04:31 PM, Jim Henderson wrote:
> On Wed, 20 Oct 2010 18:55:25 +0100, Orchid XP v8 wrote:
>
>> When you fire
>> up a debugger with support for breakpoints, literally THE FIRST THING
>> you're going to do is try to stick breakpoints on top-level functions.
>> How did this miss this?!
>
> Not me, because it seems obvious that only code that executes can be
> halted by a breakpoint.  I can't think of a debugger I've ever used that
> lets you set a breakpoint on non-executable code.  Or if I have, I've
> never needed to use that functionality.

It's pretty self-evident that if you put a breakpoint on the name of a 
function, you want it to break every time that function is called.

(It's also pretty self-evident that having some visual feedback about 
where you can and can't put breakpoints would help enourmously.)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message