LF95 Linux User's Guide - Lahey Computer Systems

Chapter 4 Command-Line Debugging with fdbonstop #n cmd[;cmd2;cmd3...;cmdn]Upon encountering breakpoint n, execute the specified fdb command(s).show breakBDisplays all breakpoints. If using the abbreviation “B”, the “B” must be upper case.Controlling Program Executioncontinue [ count ]Continues program execution until a breakpoint's count reaches count. Then, execution stops.If omitted, count defaults to 1 and the execution is interrupted at the next breakpoint. Programexecution is continued without the program being notified of a signal, even if the programwas broken by that signal. In this case, program execution is usually interrupted later whenthe program is broken again at the same instruction.silentcontinue [ count ]Same as Continue but if a signal breaks a program, the program is notified of that signal whenprogram execution is continued.step [ count ]Executes the next count lines, including the current line. If omitted, count defaults to 1, andonly the current line is executed. If a function or subroutine call is encountered, execution“steps into” that procedure.silentstep [ count ]Same as Step but if a signal breaks a program, the program is notified of that signal whenprogram execution is continued.stepi [ count ]Executes the next count machine language instructions, including the current instruction. Ifomitted, count defaults to 1, and only the current instruction is executed.silentstepi [ count ]Same as stepi but if a signal breaks a program, the program is notified of that signal whenprogram execution is continued.72 Lahey/Fujitsu Linux64 Fortran User’s Guide