This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug cli/17820] set history size unlimited in ~/.gdbinit disables history


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

--- Comment #4 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=2093d2d31460dc351145c4c295ea4a101e0c5aed

commit 2093d2d31460dc351145c4c295ea4a101e0c5aed
Author: Patrick Palka <patrick@parcs.ath.cx>
Date:   Thu Jun 4 10:12:27 2015 -0400

    Don't truncate the history file when history size is unlimited

    We still do not handle "set history size unlimited" correctly.  In
    particular, after writing to the history file, we truncate the history
    even if it is unlimited.

    This patch makes sure that we do not call history_truncate_file() if the
    history is not stifled (i.e. if it's unlimited).  This bug causes the
    history file to be truncated to zero on exit when one has "set history
    size unlimited" in their gdbinit file.  Although this code exists in GDB
    7.8, the bug is masked by a pre-existing bug that's been only fixed in
    GDB 7.9 (PR gdb/17820).

    gdb/ChangeLog:

        * top.c (gdb_safe_append_history): Do not call
        history_truncate_file if the history is not stifled.

    gdb/testsuite/ChangeLog:

        * gdb.base/gdbinit-history.exp: Add test case to check that
        an unlimited history file does not get truncated on exit.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]