There is a delicate problem with run profiles and debugger (and run). We can't use a cloned version due to the dbxgui is currently using it. It wants to set values in the project's run profile. And we can't use the original version because on Windows we need the modified PATH which is in the clone. Added this hack that meidigates the regression:

DbgActionHandler.java:
    private void doExecute(final String executable, final DebuggerManager dm, final InputOutput io) {
	final Configuration configuration = pae.getConfiguration();
        final RunProfile profile;
        // The following is a hack to work around issues with dbxgui interaction with run profile.
        // We can't use the clone becasue of dbxgui and and we can't use the original because of on windows we want to use a modified PATH.
        // We need to figure out a better solution but this should work for now (with no regressions)
        // See CR xxxxxx
        int platform = ((MakeConfiguration) configuration).getDevelopmentHost().getBuildPlatform();
        if (platform == PlatformTypes.PLATFORM_WINDOWS) {
            profile = pae.getProfile(); // Use clone on windows because of modified PATH
        } else {
            profile = configuration.getProfile(); // Don't use clone on Solaris/Linux beacuse of interaction with dbxgui. It sets values with for instance runargs xxx ...
        }

We will need to rethink how we handle this and come up with a better solution, for instance asking dbxgui not to modify run profile.