This repository has been archived by the owner on Sep 2, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 128
fput doesn't work #30
Comments
On what device? |
You mean, we can use a worse API for the sake of broken systems that are missing important APIs that happen to be accessed by calling open(2) on strings beginning with "/proc"? I'll work around the lack of /proc/self/exe support, but I'm keeping it in the Linux case, because execing /proc/self/exe is strictly better than execing orig_argv0 when someone might be replacing the program at the same time. |
Should work now. Thanks for the report. |
Confirmed. Thanks for fixing! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(also I believe the docs are incorrect: "Retrieve a file from device." Probably should be "Store a file on the device")
This is what I get when I use it:
$ fb-adb fput /tmp/libkeyboard.so /data/local/tmp/foo.so
fb-adb fput: execvpe("/proc/self/exe"): No such file or directory
The text was updated successfully, but these errors were encountered: