bc460514b9
When GDB reads a nonsensical value for the GDBHISTSIZE environment variable, i.e. one that is non-numeric or negative, GDB then sets its history size to 0. This behavior is annoying and also inconsistent with the behavior of bash. This patch makes the behavior of invalid GDBHISTSIZE consistent with how bash handles HISTSIZE. When we encounter a null or out-of-range GDBHISTSIZE (outside of [0, INT_MAX]) we now set the history size to unlimited instead of 0. When we encounter a non-numeric GDBHISTSIZE we do nothing. gdb/ChangeLog: PR gdb/16999 * NEWS: Mention new GDBHISTSIZE behavior. * top.c (init_history): For null or out-of-range GDBHISTSIZE, set history size to unlimited. Ignore non-numeric GDBHISTSIZE. gdb/doc/ChangeLog: PR gdb/16999 * gdb.texinfo (Command History): Mention new GDBHISTSIZE behavior. gdb/testsuite/ChangeLog: PR gdb/16999 * gdb.base/gdbhistsize-history.exp: New test. |
||
---|---|---|
.. | ||
a4rc.sed | ||
agentexpr.texi | ||
all-cfg.texi | ||
annotate.texinfo | ||
ChangeLog | ||
doxy-index.in | ||
Doxyfile-base.in | ||
Doxyfile-gdb-api.in | ||
Doxyfile-gdb-xref.in | ||
Doxyfile-gdbserver.in | ||
fdl.texi | ||
filter-for-doxygen | ||
filter-params.pl | ||
gdb.texinfo | ||
gpl.texi | ||
guile.texi | ||
lpsrc.sed | ||
Makefile.in | ||
observer.texi | ||
psrc.sed | ||
python.texi | ||
refcard.tex | ||
stabs.texinfo | ||
stack_frame.eps | ||
stack_frame.pdf | ||
stack_frame.png | ||
stack_frame.svg | ||
stack_frame.txt |