When I made commit
9a6c7d9c021cfeb290d76584db7a01e57e7c3d4e, which
C++-fied gdb/common/environ.[ch], I mistakenly altered the behaviour
of the 'unset environment' command. This command, which should delete
all environment variables, is now resetting the list of variables to
the state they were when GDB was started.
This commit fixes this regression, and also adds a test on
gdb.base/environ.exp which really checks if 'unset environment'
worked.
gdb/ChangeLog:
2017-08-15 Sergio Durigan Junior <sergiodj@redhat.com>
PR gdb/21954
* infcmd.c (unset_environment_command): Use the 'clear' method on
the environment instead of resetting it.
gdb/testsuite/ChangeLog:
2017-08-15 Sergio Durigan Junior <sergiodj@redhat.com>
PR gdb/21954
* gdb.base/environ.exp: Add test to check if 'unset environment'
works.
+2017-08-15 Sergio Durigan Junior <sergiodj@redhat.com>
+
+ PR gdb/21954
+ * infcmd.c (unset_environment_command): Use the 'clear' method on
+ the environment instead of resetting it.
+
2017-08-15 John Baldwin <jhb@FreeBSD.org>
* fbsd-nat.c (fbsd_convert_siginfo): Fix compile on big-endian
/* If there is no argument, delete all environment variables.
Ask for confirmation if reading from the terminal. */
if (!from_tty || query (_("Delete all environment variables? ")))
- current_inferior ()->environment = gdb_environ::from_host_environ ();
+ current_inferior ()->environment.clear ();
}
else
current_inferior ()->environment.unset (var);
+2017-08-15 Sergio Durigan Junior <sergiodj@redhat.com>
+
+ PR gdb/21954
+ * gdb.base/environ.exp: Add test to check if 'unset environment'
+ works.
+
2017-08-14 Andreas Arnez <arnez@linux.vnet.ibm.com>
* lib/gdb.exp (universal_compile_options): New caching proc.
"Delete all environment variables. .y or n. $" \
"y"
+gdb_test_no_output "show environment" \
+ "all environment variables have been unset"
+
# Verify that we can set a specific environment variable.
test_set_show_env_var "EDITOR" "emacs" "set environment variable"