erewalk / qextserialport

Automatically exported from code.google.com/p/qextserialport
Other
0 stars 0 forks source link

fix USB-serial driver issue; possible kernel dead lock #164

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which version of QextSerialPort are you using?
0394a5d33beb7f585b5c9dfac7967e6f67389006 (latest as of jun 13th 2013)

What steps will reproduce the problem?
1. use a Keyspan USA-19HS USB-serial convert
2. read & write several times to the port

What is the expected output? What do you see instead?
The program blocks at qextserialport_win.cpp:320. This is a driver fault. The 
program cannot be closed by the task manager, because it is stuck inside the 
kernel.
Using other USB-serial converters, one would get an ERROR_INVALID_PARAMETER 
(and no kernel dead lock, because of better drivers). I'm unsure why this 
happens in the first place, because the manual reset event IS signaled at the 
time of the WaitCommEvent call.

What version of the product are you using? On what operating system?
Win8

Please provide any additional information below.
The attached patch fixes the problem (but it is a workaraound).

Original issue reported on code.google.com by sebastia...@gmail.com on 13 Jun 2013 at 8:12

Attachments: