Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Using the Environment tab

What the current solution seems to do it is to assume that the environment is empty when launching GDB.
This is not the case, since GDB takes its env from the shell (well, on Linux that is what I saw).
So, if I tell it to replace the env, I see commands to set my new variables (but not delete the existing env).
If I tell it to add to the env, I see commands to set my new vars, but before that, it sets ALL variables of
the existing env.
I'll open a bug.

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
Sent: Monday, February 15, 2010 2:33 PM
To: CDT General developers list.; 'CDT General developers list.'
Subject: Re: [cdt-dev] Using the Environment tab

My expectations are the same as yours. Does the launch code not check the setting, or fumble it somewhere along the line?


At 12:58 PM 2/15/2010, Marc Khouzam wrote:
Content-Language: en-US
Content-Type: multipart/alternative;

I'm trying to understand how the Environment launch tab is supposed to affect the debug session. 
When selecting the "Append env to native env", I expect to add/modify variables to the existing environment,
but when choosing "Replace native env with specified env", I expect to replace the existing environment with
the newly defined variables.  Is that right?
I'm asking because I don't see CDI-GDB clearing the native environment when choosing "Replace native env".
If the tab is supposed to work as I describe above, I'll open a bug.
cdt-dev mailing list

Back to the top