-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unable to start debugging. Launch options string provided by the project system is invalid. The type initializer for 'System.Xml.Serialization.XmlSerializationReader' threw an exception" when debugging #792
Comments
Confirmed this happens on 0.11.3 but not 0.11.2 |
Clone: microsoft/vscode#27875 |
@AlanRosenthal Is this with Launch or attach? If you try stable with your project does it happen? I tried the scenario with my hello world app on Ubuntu 16-04 with Insiders and 0.11.3 and debugging works fine. |
@pieandcakes: launch FWIW I'm using arm-none-eabi-gdb-py not regular gdb |
@AlanRosenthal Probably going to need more repro steps. Can you enable |
Please also provide the version and type of gdb everyone is using. I am trying to reproduce this so I can find what the problem is. Also please provide a launch.json so I can try the same settings. Thanks |
gdb on ubuntu 7.11.1 |
I don't see any extra in the debug console:
|
Sorry was looking at the developer console - not the debug console |
@AlanRosenthal thanks. That helps a lot. |
@AlanRosenthal Would you be able to provide me your launch.json? If you don't want to share it publicly, can you email it to me? My email address is in my profile. Thanks |
|
Seeing this on Ubuntu 14.04, todays VSCode 1.13-insiders and ms-vscode.cpptools 0.11.3, gdb 7.7.1 and launch config: microsoft/vscode#18195 (comment) |
@AlanRosenthal Can you go to ~/.vscode/extensions/msvscode.cpptools-/debugAdapters/bin and remove the file |
Looks like its working! |
@AlanRosenthal Thanks. It was a file added for windows, but for some reason on some versions of mono on Linux it doesn't understand the file. It took me 3 machines to get a repro here. I will make an update to rename the file on non-windows machines to fix the scenario. In the meantime, the work around is: |
@chrmarti Due to a manual edit of the package.json version number to 0.11.3, the folder it creates is 0.11.2 still, but everything else should be okay. |
@chrmarti if you have one in the 0.11.2 folder location, try and remove it and it should work. There was an issue with the last extension release where the version number was manually edited but might not have been done correctly. |
@pieandcakes The file is not there, only those shown in the above screenshot. |
@chrmarti you are in the wrong folder. Its |
Debug adapters
…On Fri, Jun 2, 2017, 7:08 PM Christof Marti ***@***.***> wrote:
I don't see that file, I only see the 0.11.2 folder (no 0.11.3 which I
have installed):
[image: screen shot 2017-06-02 at 3 39 39 pm]
<https://cloud.githubusercontent.com/assets/9205389/26747359/13e54adc-47aa-11e7-8d12-d66433b5e1e4.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#792 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOqwQV4mmwXD-pZzIe3zwsY-kyIcBZpks5sAI_dgaJpZM4NteVz>
.
|
@pieandcakes had same problem on Mac OS, your solution worked for me!
|
Thank you everyone. Version |
You seem to have this issue again under 0.13.0. I deleted the aforementioned file, and all is now well. I'm running under Ubuntu 16.04. |
@endorph-soft Can you verify that you have I create a clean Ubuntu machine, installed VSCode, installed the 0.13.0 of the extension and reloaded it per the UI and it looks like I have the |
I had both of them. I'm using an offline installation, so I originally installed the extension on another machine. I then copied the extension folder to the other machine. This copied folder only contained It may just be weirdness caused by the unconventional installation method? |
@endorph-soft Possibly weirdness with offline installation. When the extension is downloaded it is named |
I tried the offline installation with the latest installers yesterday and the file has not been renamed on my machine (Ubuntu 16.04), so the bug seem to persist in the offline installation packages. |
Only the Win32 offline installation package includes that file. I thought it would be silly to package in a file that would immediately need to be removed or renamed, so I simply didn't include it for the Mac/Linux versions. The reason it exists in the online version is because we don't maintain duplicate download packages for each platform. |
messageService.ts:125 Unable to start debugging. Launch options string provided by the project system is invalid. The type initializer for 'System.Xml.Serialization.XmlSerializationReader' threw an exception. e.doShow @ messageService.ts:125 e.show @ messageService.ts:104 (anonymous) @ debugService.ts:843 v @ winjs.base.raw.js:1209 enter @ winjs.base.raw.js:901 _run @ winjs.base.raw.js:1068 _chainedError @ winjs.base.raw.js:1031 n @ winjs.base.raw.js:736 then @ winjs.base.raw.js:1436 enter @ winjs.base.raw.js:747 _run @ winjs.base.raw.js:1068 _setCompleteValue @ winjs.base.raw.js:1052 v @ winjs.base.raw.js:1209 enter @ winjs.base.raw.js:901 _run @ winjs.base.raw.js:1068 _error @ winjs.base.raw.js:1041 (anonymous) @ v8Protocol.ts:53 e.dispatch @ v8Protocol.ts:136 e.handleData @ v8Protocol.ts:104 (anonymous) @ v8Protocol.ts:41 emitOne @ events.js:96 emit @ events.js:188 readableAddChunk @ _stream_readable.js:176 Readable.push @ _stream_readable.js:134 onread @ net.js:551
The text was updated successfully, but these errors were encountered: