[Bug 59720] The environment variable are not set when debugging
John Birch
jbb at kdevelop.org
Thu Jul 3 09:13:05 UTC 2003
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=59720
------- Additional Comments From jbb at kdevelop.org 2003-07-03 09:12 -------
Here's the text of a mail I sent to kdevelop-devel mailing list on 25 June 2003
This explains the problem and a way to fix it. I have not fixed this yet :(
Maybe someone will beat me to it :)
Hi,
I want to be able to get the environment variables for any c/c++ type project
ie autoproject, trollproject etc.
The following code (in gdbcontroller.cpp:1276) works for troll projects but
doesn't work for autoprojects :(
QString project_mananger_key =
(DomUtil::readEntry(dom,"general/projectmanagement")).lower();
DomUtil::PairList envvars =
DomUtil::readPairListEntry(dom, "/" + project_mananger_key +
"/run/envvars",
"envvar", "name", "value");
because project_mananger_key = kdevkdeautoproject, but it needs to be
kdevautoproject. The troll project sets it to kdevtrollproject which just
happens to be correct for that type of project.
I think these run options don't need to be in a sub option of the project
type. This would mean we access the values like so
DomUtil::PairList envvars =
DomUtil::readPairListEntry(dom, "/run/envvars",
"envvar", "name", "value");
(I hope I'm understanding the way this Dom stuff is supposed to be working)
If no-one objects, I'll change this to remove run as a sub option and in the
process fix this bug.
jbb
More information about the KDevelop-devel
mailing list