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

["ezyang at mit dot edu" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 16999
           Summary: HISTSIZE behavior should match Bash's
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: ezyang at mit dot edu

Currently, if a HISTSIZE is passed to gdb which atoi cannot parse, gdb decides
that the desired history size is zero. This is not so great; usually people
want their history size to be infinite and not zero, especially seeing as this
behavior is different from that of bash, which assumes /infinite/ history size
when the value of HISTSIZE is empty. Thus, there is an annoying situation where
'export HISTSIZE=INFINITE' causes Bash to keep infinite history, but gdb to
keep zero history! To make matters worse, the environment variable overrides
the setting in .gdbinit. Please consider setting history_size_setshow_var to
the maximum signed integer (since readline uses a signed int) when it is not
parseable.

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