There is an error in XML document

Sysprogs forums Forums VisualGDB There is an error in XML document

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #7285
    osnwt
    Participant

    Hello,

    Used VisualGDB a lot for Linux projects. All was fine till some day. But suddenly it started complaining “Cannot perform inline build: There is an error in XML document (148, 23)”, and the build is “running” but nothing happens, I have to stop it by a command to close the solution. If the behavior starts to occur, it is exactly the same for old existing projects as well as when I try to create a new “Hello world” Linux project with VisualGDB. It even cannot create new demo.

    More details (probably irrelevant, but who knows): I have an “imported” linux project to be built via ssh natively. The sources are on a Windows computer. The VisualGDB project was created in a separate directory and references to the source directory. Sources are copied to linux to be built. I need two copies of this project to be built on two different linux boards. So I made two VisualGDB projects which both refer to the same source and open two copies of VisualStudio. Changes of any source immediately reloaded into the other VisualStudio.

    I have never seen such behavior till now. Do you have any ideas what is the XML document it refers to, and what can I do?

    Thanks!

    #7286
    osnwt
    Participant

    Here is some verbose output:

    1>------ Build started: Project: trsim1.vgdb, Configuration: Debug Win32 ------
    1>  VisualGDB: using project file C:\trsim1.vgdb\trsim1.vgdb.vcxproj
    1>  VisualGDB: using solution file C:\trsim1.vgdb\trsim1.vgdb.sln
    1>  VisualGDB: using configuration Debug
    1>  VisualGDB: Trying to detect if your Makefiles need updating... Using configuration: Debug|Win32
    1>  SSH: Looking up host...
    1>  SSH: Connecting...
    1>  SSH: Handshaking...
    1>  SSH: Checking key...
    1>  SSH: Authenticating...
    1>  Build/launch failed: В документе XML (148, 23) присутствует ошибка.
    1>  ------------------------------
    1>  Detailed exception info:
    1>  System.InvalidOperationException: В документе XML (148, 23) присутствует ошибка. ---> System.Xml.XmlException: "", шестнадцатеричное значение 0x1B, является недопустимым знаком., строка 148, позиция 23.
    1>     в System.Xml.XmlTextReaderImpl.Throw(Exception e)
    1>     в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
    1>     в System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args)
    1>     в System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
    1>     в System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType)
    1>     в System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
    1>     в System.Xml.XmlTextReaderImpl.ParseText()
    1>     в System.Xml.XmlTextReaderImpl.ParseElementContent()
    1>     в System.Xml.XmlTextReaderImpl.Read()
    1>     в System.Xml.XmlTextReader.Read()
    1>     в System.Xml.XmlReader.ReadElementString()
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read2_Record(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read3_ModifiedEnvirionment(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read4_HostSettings(Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read5_HostWideSettingsCollection(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read6_HostWideSettingsCollection()
    1>     --- Конец трассировки внутреннего стека исключений ---
    1>     в System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
    1>     в System.Xml.Serialization.XmlSerializer.Deserialize(Stream stream)
    1>     в BSPEngine.XmlTools.LoadObject[_Ty](String xmlFile, Type[] extraTypes)
    1>     в VisualGDB.Backend.SharedXmlSettingsContainer`1.c()
    1>     в ft.a()
    1>     в ft..ctor(yk A_0, SSHConnectionSettings A_1, Boolean A_2, le A_3)
    1>     в q8.a(String A_0, String A_1)
    1>     в q8.b.a(String A_0, String A_1, a A_2)
    1>     в q8.a(RemoteHostSettings A_0)
    1>     в rx.a(RemoteHostSettings A_0, Boolean A_1)
    1>     в d7.a(SourceTransferAction A_0, SourceCache A_1, aj3 A_2, Int32& A_3)
    1>     в acu.a(Boolean A_0, Boolean& A_1)
    1>     в ace.a(BuildMode A_0, a A_1)
    1>     в ace.b(BuildMode A_0, a A_1)
    1>     в no.a(String A_0, String A_1, BuildMode A_2, ael A_3, String A_4, String A_5)
    1>     в no.a(String[] A_0)
    1>  ------------------------------
    1>  Detailed exception info:
    1>  System.Xml.XmlException: "", шестнадцатеричное значение 0x1B, является недопустимым знаком., строка 148, позиция 23.
    1>     в System.Xml.XmlTextReaderImpl.Throw(Exception e)
    1>     в System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
    1>     в System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args)
    1>     в System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
    1>     в System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType)
    1>     в System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
    1>     в System.Xml.XmlTextReaderImpl.ParseText()
    1>     в System.Xml.XmlTextReaderImpl.ParseElementContent()
    1>     в System.Xml.XmlTextReaderImpl.Read()
    1>     в System.Xml.XmlTextReader.Read()
    1>     в System.Xml.XmlReader.ReadElementString()
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read2_Record(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read3_ModifiedEnvirionment(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read4_HostSettings(Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read5_HostWideSettingsCollection(Boolean isNullable, Boolean checkType)
    1>     в Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderHostWideSettingsCollection.Read6_HostWideSettingsCollection()
    1>  ------------------------------
    1>  Product version: 5.0.18.529
    #7301
    support
    Keymaster

    Hi,

    Most likely one of the .sshconnection files in %APPDATA%\VisualGDB\SSHConnections got corrupt. Please try removing those files and recreating the connection via Tools->SSH Connections.

    #7308
    osnwt
    Participant

    Unfortunately, no. All files are ok.

    Also, I created a new connection using IP address as a host name, login/password authentication. Then started to create a new project, and got the same error in XML document 148, 23.

    I should tell that user has been logged in successfully in both cases, and error is shown after login.

    Please tell me what else can I do to help debugging this issue.

    • This reply was modified 8 years, 11 months ago by osnwt.
    #7317
    support
    Keymaster

    Hi,

    The only other place that could be related is the HostWideSettings.xml file in the same directory. Please try removing that file.

    #7335
    osnwt
    Participant

    Removal of that file has helped.

    Thank you!

    #7339
    support
    Keymaster

    No problem. Enjoy VisualGDB!

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.