Fix PR gdb/21954: make 'unset environment' work again
authorSergio Durigan Junior <sergiodj@redhat.com>
Tue, 15 Aug 2017 17:49:18 +0000 (13:49 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Tue, 15 Aug 2017 17:49:18 +0000 (13:49 -0400)
commit206726fbfdd521fbb184daedb71b85030453bf0b
treef9a53185e79ea333158cf97e907d824e4716565a
parent0335ac6d12906bfb4b48410d8a7229c21c727cf2
Fix PR gdb/21954: make 'unset environment' work again

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.
gdb/ChangeLog
gdb/infcmd.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/environ.exp
This page took 0.0253 seconds and 4 git commands to generate.