search

techl / MonoRemoteDebugger

Other
83 stars 18 forks source link

ArgumentNullException in Version 1.3 #40

Closed jikelmon closed 7 years ago

jikelmon commented 7 years ago

Installed product versions

Description

"System.ArgumentNullException" at "MonoRemoteDebugger.SharedLib.Server.ClientSession.StartDebugging" leads to crash.

Steps to recreate

  1. Start MonoRemoteDebugger 1.3.0 on RPi
  2. Start remote debugging on VS
  3. MonoRemoteDebugger throws "System.ArgumentNullException" exception

Current behavior

RemoteDebugging process throws exception.

Full debug message:

2017-07-25 15:30:22.5523|INFO|MonoRemoteDebugger.SharedLib.Server.ClientSession|DebugContent-Message received 2017-07-25 15:30:22.5581|ERROR|MonoRemoteDebugger.SharedLib.Server.ClientSession|System.ArgumentNullException: Value cannot be null. Parameter name: path2 at System.IO.Path.Combine (System.String path1, System.String path2) [0x00011] in <9bc402929dff445999ba28b84751d284>:0 at MonoRemoteDebugger.SharedLib.Server.ClientSession.StartDebugging (MonoRemoteDebugger.SharedLib.StartDebuggingMessage msg) [0x00032] in <774b6a28ae47478e896b75e30caf594e>:0 at MonoRemoteDebugger.SharedLib.Server.ClientSession.HandleSession () [0x000a8] in <774b6a28ae47478e896b75e30caf594e>:0 2017-07-25 15:30:22.5675|INFO|MonoRemoteDebugger.SharedLib.Server.MonoDebugServer|Waiting for client

Expected behavior

RemoteDebugging without any problems as in v1.2.1.

techcap commented 7 years ago

Did you update the server also?

jikelmon commented 7 years ago

My bad. There was an VS extension update to 1.3.0 as well which did not show up when i checked for an update. Removed the extension, did a reboot of my pc and VS and boom, 1.3.0 showed up in the extension repo. Now everything works fine.

Sorry for bothering you and opening an issue...

Thank you very much!!

techcap commented 7 years ago

👍