This is the mail archive of the
mailing list for the GDB project.
Re: [RFA] Environment variables passed to inferior by MinGW build (PR 10989)
- From: Eli Zaretskii <eliz at gnu dot org>
- To: gdb-patches at sourceware dot org
- Date: Tue, 04 Oct 2011 05:29:18 -0400
- Subject: Re: [RFA] Environment variables passed to inferior by MinGW build (PR 10989)
- References: <E1R2jDx-00035B-Fq@fencepost.gnu.org> <E1R5YPa-0007H0-0B@fencepost.gnu.org> <E1R7mEx-0003rs-PZ@fencepost.gnu.org> <4E7FBF9E.firstname.lastname@example.org> <20110926171511.GJ17681@adacore.com> <20111004075325.GB13895@calimero.vinschen.de>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Tue, 4 Oct 2011 09:53:26 +0200
> From: Corinna Vinschen <email@example.com>
> Reply-To: firstname.lastname@example.org
> I was on vacation and I'm also not the area maintainer for windows-nat.c.
No worries, I hope you had a good time ;-)
I CC'ed you because you made the change that I partially undid, and
also participated in some of the discussions I cited.
> Eli's patch is ok, IMHO, but it's a pity that Pierre never followed up
> to http://sourceware.org/ml/gdb-patches/2011-04/msg00351.html since that
> means that now setting environment variables works in Mingw, but not in
Could you elaborate why the behavior on Cygwin is incorrect? AFAICT,
Pierre's changes didn't get into GDB, so GDB still works as it did
before, and your changes that introduced the call to cygwin_internal
were supposed to fix the issue of "set environment" and "unset
environment", right? Not that I understand exactly what
cygwin_internal does in that case and how it works.
> So, as far as I can see, PR #10989 should not have been closed
But that bug report is for the MinGW host and target only, so if
Cygwin has a similar problem, it's a different issue and probably also
a different solution.
OTOH, if the same code I re-introduced will work for Cygwin, it should
be a simple matter to remove the #if conditionals. Am I missing