[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Using the Environment tab
|
I've opened
(I should put a [dsf] tag on it for
feature-parity ;-))
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of
Marc Khouzam
Sent: Monday, February 15, 2010 3:24 PM
To:
'CDT General developers list.'
Subject: 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.
Thanks
My expectations are the same as yours. Does the launch code not
check the setting, or fumble it somewhere along the
line?
John
At 12:58 PM 2/15/2010, Marc Khouzam wrote:
Content-Language:
en-US
Content-Type:
multipart/alternative;
boundary="_000_F7CE05678329534C957159168FA70DEC51F2D9FC26EUSAACMS0703e_"
Hi,
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.
Thanks
Marc
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev