I saw some test cases in gdb.base/default.exp and gdb.base/setshow.exp
are enabling the history saving.
Hence .gdb_history file is modified with history information even
though, by default, we have History saving disabled.
So we should modify GDB test cases so that history saving should stay
off for all test cases.
ChangeLog:
2013-05-13 Muhammad Bilal <mbilal@codesourcery.com>
* gdb.base/default.exp: Disable history saving.
* gdb.base/setshow.exp: Likewise.
+2013-05-13 Muhammad Bilal <mbilal@codesourcery.com>
+
+ * gdb.base/default.exp: Disable history saving.
+ * gdb.base/setshow.exp: Likewise.
+
2013-05-10 Pedro Alves <palves@redhat.com>
PR remote/15455
}
}
}
+#history saving should stay disabled
+gdb_test_no_output "set history save off" "set history save off"
#test stepi "si" abbreviation
gdb_test "si" "The program is not being run." "stepi \"si\" abbreviation"
#test stepi
gdb_test_no_output "set history save on" "set history save on"
#test show history save on
gdb_test "show history save" "Saving of the history record on exit is on..*" "show history save (on)"
+#history saving should stay disabled
+gdb_test_no_output "set history save off" "set history save off"
#test set history size 100
gdb_test_no_output "set history size 100" "set history size 100"
#test show history size 100