This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] Use getenv instead of gdb_environ on mi-cmd-env.c
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Mon, 19 Jun 2017 00:40:02 -0400
- Subject: [binutils-gdb] Use getenv instead of gdb_environ on mi-cmd-env.c
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 1c8e01c96054973c50ec1dec2f220af4734e1de5 ***
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Branch: master
Commit: 1c8e01c96054973c50ec1dec2f220af4734e1de5
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.