diff options
| author | David Carlton <carlton@bactrian.org> | 2003-04-16 19:57:09 +0000 |
|---|---|---|
| committer | David Carlton <carlton@bactrian.org> | 2003-04-16 19:57:09 +0000 |
| commit | 0bb428781c4782c6236beb58c06052dccd382aa1 (patch) | |
| tree | c2745e3799c869e29769a81c22cc151fdbe84a97 /gdb/objfiles.h | |
| parent | 8ddfa96fcd388fb183d7aac8befd08c138e105dd (diff) | |
| download | gdb-0bb428781c4782c6236beb58c06052dccd382aa1.zip gdb-0bb428781c4782c6236beb58c06052dccd382aa1.tar.gz gdb-0bb428781c4782c6236beb58c06052dccd382aa1.tar.bz2 | |
2003-04-16 David Carlton <carlton@bactrian.org>
* Merge with mainline; tag is carlton_dictionary-20030416-merge.
Diffstat (limited to 'gdb/objfiles.h')
| -rw-r--r-- | gdb/objfiles.h | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/gdb/objfiles.h b/gdb/objfiles.h index e710263..f747a68 100644 --- a/gdb/objfiles.h +++ b/gdb/objfiles.h @@ -65,14 +65,15 @@ struct htab; confused. However, we almost always have debugging information available for main(). - These variables are used to save the range of PC values which are valid - within the main() function and within the function containing the process - entry point. If we always consider the frame for main() as the outermost - frame when debugging user code, and the frame for the process entry - point function as the outermost frame when debugging startup code, then - all we have to do is have FRAME_CHAIN_VALID return false whenever a - frame's current PC is within the range specified by these variables. - In essence, we set "ceilings" in the frame chain beyond which we will + These variables are used to save the range of PC values which are + valid within the main() function and within the function containing + the process entry point. If we always consider the frame for + main() as the outermost frame when debugging user code, and the + frame for the process entry point function as the outermost frame + when debugging startup code, then all we have to do is have + DEPRECATED_FRAME_CHAIN_VALID return false whenever a frame's + current PC is within the range specified by these variables. In + essence, we set "ceilings" in the frame chain beyond which we will not proceed when following the frame chain back up the stack. A nice side effect is that we can still debug startup code without @@ -83,9 +84,10 @@ struct htab; information but we do have usable information for main(), backtraces from user code don't go wandering off into the startup code. - To use this method, define your FRAME_CHAIN_VALID macro like: + To use this method, define your DEPRECATED_FRAME_CHAIN_VALID macro + like: - #define FRAME_CHAIN_VALID(chain, thisframe) \ + #define DEPRECATED_FRAME_CHAIN_VALID(chain, thisframe) \ (chain != 0 \ && !(inside_main_func ((thisframe)->pc)) \ && !(inside_entry_func ((thisframe)->pc))) |