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

Opening a serial port in use causes the program to crash #133

Closed
NAW77 opened this Issue Feb 12, 2014 · 1 comment

Comments

2 participants
@NAW77

NAW77 commented Feb 12, 2014

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.

@FauxFaux

This comment has been minimized.

Show comment
Hide comment
@FauxFaux

FauxFaux Feb 12, 2014

Owner

Yeah, I can reproduce this. It's a bug in GH-110: ada3951#diff-88776592a9f52e2b3f2939253efbc5ecL321

The error handling here isn't great and realhost is ending up unset for some types of connections. I'll re-think the error handling later.

Owner

FauxFaux commented Feb 12, 2014

Yeah, I can reproduce this. It's a bug in GH-110: ada3951#diff-88776592a9f52e2b3f2939253efbc5ecL321

The error handling here isn't great and realhost is ending up unset for some types of connections. I'll re-think the error handling later.

FauxFaux added a commit that referenced this issue Feb 21, 2014

GH-133: Crash on initial connection fail (serial)
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.

@FauxFaux FauxFaux closed this Feb 21, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment