[Bug gdb/16999] HISTSIZE behavior should match Bash's

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16999

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bc460514b9db46a491c2c39cd118b02608742968

commit bc460514b9db46a491c2c39cd118b02608742968
Author: Patrick Palka <patrick@parcs.ath.cx>
Date:   Tue May 12 06:50:26 2015 -0400

    Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999]

    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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.