suggestion for auto breakpoints

Duane Voth duanev at interactivesi.com
Tue Feb 1 21:32:14 GMT 2000


A useful way to debug new programs is to place a break point
inside each function and even inside each if/else and switch
statement.  This can create quite a few break points but with
awesome development tools like kdevelop, tracing through each
path of an entire program becomes a reasonable task - AND it
allows for some of the best code verification testing we've
ever had.

What is great is that (once the breakpoint/line number tracking
problem is fixed) the breakpoints will tend to linger around
until the developer specifically turns each one off allowing
the tools to track which lines of code have not been executed
and checked.

How about an option per function, file, or project that would
add breakpoints in such a fashion? (configurable as to stopping
for branch statements of course)  Imo, a menu item "Set multiple
breakpoints" could go right above "Clear all breakpoints" (which
btw is immediately useful!) and provide a sub menu for function,
file, or project.

comments?

duane




More information about the KDevelop mailing list