Bug 39424

Summary: Compiler options, Add configuration produces invalid xml
Product: [Applications] kdevelop Reporter: olistrut
Component: kdevelop 2.x (obsolete)Assignee: KDevelop-Devel List <kdevelop-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description olistrut 2002-03-17 18:48:31 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.1 Beta 2 (using KDE 2.2.2 )
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: Not Specified

Steps to reproduce:

Follow http://www.uv-ac.de/ipaqhelp/index-7.html to set up a new project but when setting up a new compiler configuration for cross compilation enter a config name that includes spaces (e.g. "ARM QT Embedded 2").

KDevelop will continue to work and will write .kdevses file on closing the project. Reloading the projects results in an error message (session file contains invalid xml).

Problem:

KDevelop uses the configuration name as a tag name in the session file :
 <CompileConfigs>
  <ARM QT Embedded 2>
    ...
effectively creating invalid XML.

Possible solutions: 
- Encode special characters (" " -> _)
- Don't allow special characters in config name
- Change DTD and make config name an attribute eg. 
 <CompileConfigs>
  <CompileConfig name = "ARM QT Embedded2">
    ...


(Submitted via bugs.kde.org)
Comment 1 Caleb Tennis 2002-10-09 22:02:20 UTC
This has been fixed in Gideon (3.0) 
Comment 2 Thomas Koch 2006-09-17 18:34:59 UTC
I still encounter the error in this environment when working with pascal-projects:
KDE Version 	3.3.2 (KDE 3.5.4, Debian Package 4:3.5.4-3 (testing/unstable))
	Application 	Integrated Development Environment
	Operating System 	Linux (i686) release 2.6.16-2-k7
	Compiler 	Target: i486-linux-gnu

Comment 3 Amilcar do Carmo Lucas 2006-09-17 20:16:33 UTC
Thomas could you provide some more info please ?
This bug is more than 4 years old!