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.

Sign up for GitHub

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

Jump to bottom

Unsupported settings do not SetLastError() under Windows (XP?) #21

Open
hparra opened this issue Jul 17, 2010 · 1 comment
Open

Unsupported settings do not SetLastError() under Windows (XP?) #21

hparra opened this issue Jul 17, 2010 · 1 comment
Labels
BUG Windows

Comments

@hparra
Copy link
Owner

hparra commented Jul 17, 2010

from asquared: "In other news, Windows (XP at least) is brain dead. From the looks of things, if you pass a baud rate or other DCB settings which happen to be unsupported by the hardware, SetCommState returns zero but doesn't SetLastError( ) in the process. This in turn causes the Ruby interpreter to crash..."
@hparra
Copy link
Owner Author

hparra commented Jul 17, 2010

The same exact behavior needs to be confirmed for Vista/7. I would like to confirm whose fault this is (OS? Ruby?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BUG Windows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hparra