This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug testsuite/18550] New: GDB's testsuite and user's shell history
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 17 Jun 2015 13:19:16 +0000
- Subject: [Bug testsuite/18550] New: GDB's testsuite and user's shell history
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18550
Bug ID: 18550
Summary: GDB's testsuite and user's shell history
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: palves at redhat dot com
Target Milestone: ---
In https://sourceware.org/ml/gdb-patches/2015-06/msg00361.html,
Pedro Alves wrote:
> For HISTSIZE, should we audit tests that might start an interactive
> shell (e.g., "(gdb) shell") and result in truncating the history file?
> Guess better would be to set HISTSIZE="" and HISTFILE=/dev/null
> or something like that so shells we start don't have a chance of
> mucking with the user's history files?
>
> Urgh, yes, we already have that issue today:
>
> $ make check RUNTESTFLAGS="gdb.base/batch-preserve-term-settings.exp"
> $ tail -n 5 ~/.bash_history
> stty || echo "not found"
> /home/pedro/gdb/mygit/build/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/pedro/gdb/mygit/build/gdb/testsuite/../data-directory -batch -ex "set height unlimited" -ex "start" --args "/home/pedro/gdb/mygit/build/gdb/testsuite/gdb.base/batch-preserve-term-settings"
> echo test_echo
> stty || echo "not found"
> exit
>
> Whoops...
--
You are receiving this mail because:
You are on the CC list for the bug.