This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
Opening a serial port in use causes the program to crash #133
Comments
|
Yeah, I can reproduce this. It's a bug in GH-110: ada3951#diff-88776592a9f52e2b3f2939253efbc5ecL321 The error handling here isn't great and |
FauxFaux
added a commit
that referenced
this issue
Feb 21, 2014
I knew that would go wrong. Dammit. Re-review that code for possible horrors. I'm still not happy with backhandle possibly being junk, but nothing should really get far enough to notice (famous last words). Still going with it being better to run stuff, than to not run it.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The original Putty 0.63 displays a window telling you that COMx is currently in use when you have another program or session using that port.
The currenty t020 build of Putty Tray just crashes if you use the same port "A problem caused the program to stop working correctly. Please close the program" with the option to Close or Debug.
If I select to debug with VStudio then I get "Unhandled exception at 0x00B38C8E in putty.exe: 0xC0000005: Access violation reading location 0xE8ED6472."
This issue happens all the time on Win8.1-x64 with a USB FTDI chipset device.
The text was updated successfully, but these errors were encountered: