You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to test binee and make sure it got the DLLs correctly, but I used a custom config ("win10_64" instead of 32). Unfortunately, it was hardcoded to use the default "win10_32" config. The code for this is here. I'm happy to put together a PR for this flag to obey a custom config that gets passed in with -c, but I'm curious if this is worthwhile or relevant. Thoughts?
Output:
root@04f06cefb9a9:~/go/src/binee# ./binee -A -c config/my_config.yaml
2019/08/19 20:34:21 file 'apisetschema.dll' not found
root@04f06cefb9a9:~/go/src/binee# cat config/my_config.yaml
root: "os/win10_64/"
root@04f06cefb9a9:~/go/src/binee# ls os/win10_64/windows/system32/
advapi32.dll apisetschema.dll crypt32.dll kernel32.dll mswsock.dll ntdll.dll secur32.dll shell32.dll shlwapi.dll user32.dll ws2_32.dll
The text was updated successfully, but these errors were encountered:
Good timing on this issue, I'm currently working on fixing that hard-coded path as we speak. This same issue is the cause of other issues relating to custom configs. PR coming shortly.
Yeah I discovered the 64bit issue pretty quickly afterwards trying to get those libraries to work, so I switched to a set of 32bit DLLs. Is there a timeline for full 64bit support?
I wanted to test binee and make sure it got the DLLs correctly, but I used a custom config ("win10_64" instead of 32). Unfortunately, it was hardcoded to use the default "win10_32" config. The code for this is here. I'm happy to put together a PR for this flag to obey a custom config that gets passed in with
-c
, but I'm curious if this is worthwhile or relevant. Thoughts?Output:
The text was updated successfully, but these errors were encountered: