diff options
Diffstat (limited to 'gdb/doc/gdb.texinfo')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index cc2391b..5dc0af0 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5951,7 +5951,7 @@ only if it is a scalar (integer, pointer, enumeration, etc). See command @kbd{set print frame-arguments} in @ref{Print Settings} for more details on how to configure the way function parameter values are printed. -@cindex value optimized out, in backtrace +@cindex optimized out, in backtrace @cindex function call arguments, optimized out If your program was compiled with optimizations, some compilers will optimize away arguments passed to functions if those arguments are @@ -5965,8 +5965,8 @@ such a backtrace might look like: @group #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) at builtin.c:993 -#1 0x6e38 in expand_macro (sym=<value optimized out>) at macro.c:242 -#2 0x6840 in expand_token (obs=0x0, t=<value optimized out>, td=0xf7fffb08) +#1 0x6e38 in expand_macro (sym=<optimized out>) at macro.c:242 +#2 0x6840 in expand_token (obs=0x0, t=<optimized out>, td=0xf7fffb08) at macro.c:71 (More stack frames follow...) @end group @@ -5974,7 +5974,7 @@ such a backtrace might look like: @noindent The values of arguments that were not saved in their stack frames are -shown as @samp{<value optimized out>}. +shown as @samp{<optimized out>}. If you need to display the values of such optimized-out arguments, either deduce that from other variables whose values depend on the one |