-
Notifications
You must be signed in to change notification settings - Fork 31
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
Interrupted system call #25
Comments
Please try this patch: diff --git a/proxy.cpp b/proxy.cpp
index beefeb2..b28b726 100644
--- a/proxy.cpp
+++ b/proxy.cpp
@@ -249,6 +249,11 @@ void *ep_loop_read(void *arg) {
ep.bEndpointAddress, transfer_type.c_str(), dir.c_str());
break;
}
+ if (rv < 0 && errno == EINTR) {
+ printf("EP%x(%s_%s): interface likely changing, stopping thread\n",
+ ep.bEndpointAddress, transfer_type.c_str(), dir.c_str());
+ break;
+ }
else if (rv < 0) {
perror("usb_raw_ep_read()");
exit(EXIT_FAILURE); |
I did something similar. I'm doing so many devices right now so I lose tack of what errors I got where. Ultimately something strange is going on with iSync transfer. I straight up pass the read threads on iSync and it keeps running otherwise it segfaults. It starts ep5 (which I'm sure is different device to device), passes flag of 0 and gets invalid Args. I know there's issues for isync. I'm getting heavy into a lot of this stuff. My cynthion from great Scott just arrived, I'll play with it a bit and come back to this. |
Commit 4a48d46 added a EINTR handler for usb_raw_ep_write but not for usb_raw_ep_read; fix this. Fixes AristoChen#25.
Hi @rlewkowicz thanks for reporting the issue, do you have any chance to see if the PR #26 (Thanks @xairy !) fixes the issue? thanks! |
I'm trying to sniff a handshake between an xbox series x and its controller. I'm sure I'll run into issues after this, but I think it's not terming correctly?
usb-proxy/proxy.cpp
Line 350 in c6454ce
Here you kill the threads, but here it exits the application with
usb_raw_ep_read(): Interrupted system call
usb-proxy/proxy.cpp
Line 254 in c6454ce
The text was updated successfully, but these errors were encountered: