TotalView Users Guide - CI Wiki

Automatically Setting Breakpoints
Automatically Setting Breakpoints
In many cases, your knowledge of what a program is doing lets you make
predictions as to where problems occurs. The following CLI macro parses
comments that you can include in a source file and, depending on the
comment’s text, sets a breakpoint or an eval point.
Following this macro is an excerpt from a program that uses it.
# make_actions: Parse a source file, and insert
# evaluation and breakpoints according to comments.
#
proc make_actions {{filename ""}} {
if {$filename == ""} {
puts "You need to specify a filename"
error "No filename"
}
# Open the program’s source file and initialize a
# few variables.
set fname [set filename]
set fsource [open $fname r]
set lineno 0
set incomment 0
# Look for "signals" that indicate the type of
# action point; they are buried in the comments.
while {[gets $fsource line] != –1} {
incr lineno
set bpline $lineno
# Look for a one-line eval point. The
# format is ... /* EVAL: some_text */.
# The text after EVAL and before the "*/" in
# the comment is assigned to "code".
if [regexp "/\\* EVAL: *(.*)\\*/" $line all code] {
dbreak $fname\#$bpline –e $code
continue
}
# Look for a multiline eval point.
if [regexp "/\\* EVAL: *(.*)" $line all code] {
# Append lines to "code".
while {[gets $fsource interiorline] != –1} {
incr lineno
# Tabs will confuse dbreak.
regsub –all \t $interiorline \
" " interiorline
218 Chapter 11: Seeing the CLI at Work