aboutsummaryrefslogtreecommitdiff
path: root/gdb/proc-api.c
diff options
context:
space:
mode:
authorSergio Durigan Junior <sergiodj@redhat.com>2017-06-16 18:10:27 -0400
committerSergio Durigan Junior <sergiodj@redhat.com>2017-06-19 00:14:00 -0400
commit1c8e01c96054973c50ec1dec2f220af4734e1de5 (patch)
tree03def41a32228b291c25526b8286c154353bcd1e /gdb/proc-api.c
parent65ce7763dfbca7f74c951767050ad2da0739869b (diff)
downloadgdb-1c8e01c96054973c50ec1dec2f220af4734e1de5.zip
gdb-1c8e01c96054973c50ec1dec2f220af4734e1de5.tar.gz
gdb-1c8e01c96054973c50ec1dec2f220af4734e1de5.tar.bz2
Use getenv instead of gdb_environ on mi-cmd-env.c
This is a spinoff of <https://sourceware.org/ml/gdb-patches/2017-06/msg00437.html>. mi-cmd-env.c is using the whole gdb_environ machinery in order to access just one variable, which can be easily replaced by a simple call to getenv. This patch does that, and doesn't cause regressions. gdb/ChangeLog: 2017-06-18 Sergio Durigan Junior <sergiodj@redhat.com> * mi/mi-cm-env.c (_initialize_mi_cmd_env): Use getenv instead of gdb_environ to access an environment variable.
Diffstat (limited to 'gdb/proc-api.c')
0 files changed, 0 insertions, 0 deletions