HP gnu source-level debugger 5992-4701 - Manual (Page 146)

The advantages include:
• You do not have to recompile and relink the entire program.
• You do not have to reload the program into the debugger.
• You can resume execution of the program from the x location.
• You can speed up the development cycle.
NOTE: Fix and Continue is only supported with the most recent versions of HP C
and HP aC++ on PA-RISC systems.
In command-line mode, you use the edit command before invoking the fix command.
The edit command has the following syntax:
edit file1 file2
where
file represents one or more source files for the current executable. If you do not specify
a file name, WDB edits the currently open source file.
When you edit a file with the edit command and save the changes, the original source
file contains the changes, even if you do not use the fix command to recompile the
program in the debugger.
14.7.1 Fix and Continue compiler dependencies
Fix and Continue is supported only for PA-RISC on HP-UX 11.x with these compilers:
• HP C/ANSI C A.11.01.20, or later
• HP aC++ A.03.25, or later
• HP Fortran 90 2.4, or later
14.7.2 Fix and Continue restrictions
Fix and Continue has the following restrictions and behaviors:
• You cannot recompile code that has been optimized.
• You cannot add, delete, or reorder the local variables and parameters in a function
currently active on the stack.
• If you x a routine in a file that contains function pointers, those function pointers
become invalid and will likely cause the program to receive a SIGSEGV error if
the pointers are used.
• You cannot change the type of a local variable, file static, global variable, or
parameter of a function.
• You cannot add any function calls that increase the size of the parameter area.
• You cannot change a local or file static or global variable to be a register variable,
and vice-versa.
146 HP-UX Configuration-Specific Information