Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] testsuite: Add a test for passing of environment variables to inferior
Date: Tue, 04 Oct 2011 14:48:00 -0000	[thread overview]
Message-ID: <000601cc82a4$a625e310$f271a930$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83zkhgrf60.fsf@gnu.org>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : mardi 4 octobre 2011 16:43
> À : gdb-patches@sourceware.org
> Objet : Re: [RFA] testsuite: Add a test for passing of environment
variables
> to inferior
> 
> > Date: Tue, 4 Oct 2011 15:45:06 +0200
> > From: Corinna Vinschen <vinschen@redhat.com>
> >
> > Yes, that would be necessary.  I'm wondering if we can't just utilze the
> > global environ variable for this and spare us all the hassle.  Something
> > along these lines:
> >
> >   char **old_env = environ;
> >   environ = in_env;
> >   cygwin_internal (CW_SYNC_WINENV);
> >   CreateProcessW (NULL environment pointer);
> >   environ = old_env;
> 
> If my reading of sync_winenv is correct, you'd need one more call to
> cygwin_internal after restoring `environ'.  Otherwise, the Windows
> environment of GDB will be left at the value passed to the inferior,
> which could have all kinds of weird unexpected effects elsewhere in
> GDB.
No, this is not enough, see my next email...

Pierre


  reply	other threads:[~2011-10-04 14:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 12:36 Pierre Muller
2011-10-04 13:45 ` Corinna Vinschen
2011-10-04 14:43   ` Eli Zaretskii
2011-10-04 14:48     ` Pierre Muller [this message]
2011-10-04 14:50   ` Pierre Muller
2011-10-04 15:13     ` Corinna Vinschen
2011-10-04 16:09       ` [RFA-v2] " Pierre Muller
2011-10-04 16:11       ` [RFA] " Pierre Muller
2011-10-05 11:40         ` Corinna Vinschen
2011-10-05 12:08           ` Pierre Muller
2011-10-05 12:52             ` Corinna Vinschen
2011-10-06 14:51               ` Christopher Faylor
2011-10-06 15:03                 ` Corinna Vinschen
2011-10-07 12:26                   ` Christopher Faylor
2011-10-07 13:53                     ` Corinna Vinschen
     [not found]       ` <12954.5351061553$1317744599@news.gmane.org>
2011-10-04 17:27         ` [RFA-v2] " Tom Tromey
2011-10-04 21:35           ` [RFA-v3] " Pierre Muller
     [not found]           ` <29288.743020925$1317764135@news.gmane.org>
2011-10-05 13:53             ` Tom Tromey
2011-10-05 14:25               ` Pierre Muller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601cc82a4$a625e310$f271a930$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox