Skip to content
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

A Command With No Data Causes Crash #33

Closed
JamesMc86 opened this issue Oct 25, 2017 · 1 comment
Closed

A Command With No Data Causes Crash #33

JamesMc86 opened this issue Oct 25, 2017 · 1 comment
Labels

Comments

@JamesMc86
Copy link
Collaborator

For some reason we have a guard that we don't read the TCP buffer if length is only TYPE_BYTES. This means the TYPE is left in the buffer and corrupts the next read.

This will result in the following exception:

Unhandled Exception: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: size
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at LabVIEW_CLI.lvComms.readMessage()
   at LabVIEW_CLI.Program.Main(String[] args)
@JamesMc86 JamesMc86 added the bug label Oct 25, 2017
@JamesMc86
Copy link
Collaborator Author

Fixed in v1.5.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant