From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: guitton@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA/mingw32] environment variables are case-insensitive on win32
Date: Mon, 10 Dec 2012 16:26:00 -0000 [thread overview]
Message-ID: <834njtc1qw.fsf@gnu.org> (raw)
In-Reply-To: <002401cdd6f0$c0b317b0$42194710$%muller@ics-cnrs.unistra.fr>
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Cc: <gdb-patches@sourceware.org>
> Date: Mon, 10 Dec 2012 17:09:37 +0100
>
> (gdb) set Test1=Mixed
> No symbol "Test1" in current context.
> (gdb) set env Test1=Mixed
> (gdb) set env test1=lower
> (gdb) set env TEST1=UPPER
> (gdb) set prompt top>
> top> r
> Starting program: e:\pas\fpc-2.6.0\bin\i386-Win32\gdbpurepython.exe
> ... Some output suppressed
> (gdb) [New Thread 5920.0xb04]
> [New Thread 5920.0x1588]
> show env
> ALLUSERSPROFILE=C:\ProgramData
> ... More output suppressed
> PROMPT=$P$G
> PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
> PUBLIC=C:\Users\Public
> RoxioCentral=C:\Program Files (x86)\Common Files\Roxio Shared\10.0\Roxio
> Central36\
> SESSIONNAME=Console
> SystemDrive=C:
> SystemRoot=C:\Windows
> TEMP=C:\Users\Pierre\AppData\Local\Temp
> test1=lower
> Test1=Mixed
> TEST1=UPPER
> ... More output suppressed
You _are_ aware that "show env" is a GDB command, right? What you
need to do is run some Windows program after pushing these variables
into the environment, and then see what that problem gets as
environment.
next prev parent reply other threads:[~2012-12-10 16:26 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 13:37 Jerome Guitton
2012-11-30 13:47 ` Eli Zaretskii
2012-11-30 14:08 ` Jerome Guitton
2012-11-30 15:27 ` Eli Zaretskii
2012-11-30 15:34 ` Jerome Guitton
2012-11-30 16:07 ` Eli Zaretskii
2012-11-30 16:29 ` Jerome Guitton
2012-11-30 18:55 ` Eli Zaretskii
2012-12-07 9:22 ` Jerome Guitton
2012-12-07 9:30 ` Eli Zaretskii
2012-12-07 10:06 ` Jerome Guitton
2012-12-07 10:06 ` Joel Brobecker
2012-12-07 10:11 ` Jerome Guitton
2012-12-07 10:18 ` Joel Brobecker
2012-11-30 19:02 ` Pedro Alves
2012-12-03 11:31 ` Jerome Guitton
2012-12-09 23:53 ` Christopher Faylor
2012-12-10 10:51 ` Jerome Guitton
2012-12-10 11:01 ` Corinna Vinschen
2012-12-10 13:50 ` Joel Brobecker
2012-12-10 15:24 ` Corinna Vinschen
2012-12-10 15:42 ` Jerome Guitton
2012-12-10 15:58 ` Corinna Vinschen
2012-12-10 16:08 ` Jerome Guitton
2012-12-10 16:09 ` Eli Zaretskii
2012-12-10 16:17 ` Corinna Vinschen
2012-12-10 16:24 ` Jerome Guitton
2012-12-10 16:24 ` Eli Zaretskii
2012-12-10 16:57 ` Corinna Vinschen
2012-12-10 20:11 ` Eli Zaretskii
2012-12-11 10:20 ` Corinna Vinschen
2012-12-11 14:25 ` Pedro Alves
2012-12-11 14:41 ` Corinna Vinschen
2012-12-11 15:07 ` Pedro Alves
2012-12-11 15:21 ` Corinna Vinschen
2012-12-11 15:23 ` Pierre Muller
2012-12-14 10:55 ` Jerome Guitton
2012-12-14 10:35 ` Jerome Guitton
2012-12-10 15:35 ` Jerome Guitton
2012-12-10 16:09 ` Pierre Muller
2012-12-10 16:18 ` 'Jerome Guitton'
2012-12-10 16:27 ` Pierre Muller
2012-12-10 16:54 ` Corinna Vinschen
2012-12-10 18:22 ` Jerome Guitton
2012-12-10 18:35 ` Pierre Muller
2012-12-10 18:36 ` 'Jerome Guitton'
2012-12-11 9:50 ` 'Jerome Guitton'
2012-12-11 16:27 ` Christopher Faylor
[not found] ` <002401cdd6f0$c0b317b0$42194710$%muller@ics-cnrs.unistra.fr>
2012-12-10 16:26 ` Eli Zaretskii [this message]
2012-12-10 16:40 ` Pierre Muller
2012-12-10 16:51 ` Jerome Guitton
2012-12-10 17:16 ` Jerome Guitton
2012-11-30 14:43 ` Pedro Alves
2012-11-30 15:03 ` Jerome Guitton
2012-11-30 15:38 ` Jerome Guitton
2012-11-30 15:41 ` Pedro Alves
2012-11-30 15:46 ` Tom Tromey
2012-11-30 15:49 ` Pedro Alves
2012-11-30 16:02 ` Jerome Guitton
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=834njtc1qw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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