Problems? Is your data what you think it is? | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Cool! ++ One thought. I have encountered an (occasional) situation where using ioctl($client, 0x8004667e, 1); fails. More reliable seems to be:
The problem seems to be that under some, unspecified (and through my best efforts, untracable), circumstances, the 'system' (I haven't figured out what part of the system), attempts to write to the third parameter. And if that is a constant (or a reference to a constant, I used ioctl($client, 0x8004667e, \1); successfully for a while), then it cannot write to it and so it traps. See ioctlsocket Function(windows) and notice that the third parameter is defined as being __inout. Whether passing a reference to a rw SV* gets correctly translated, I'm not sure, but it doesn't seem to harm. Maybe that would 'fix' the problem with OpenSSH? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^2: Non-blocking Reads from Pipe Filehandle
by BrowserUk
|
|