We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When parsing an ELF with -R, oki includes single quotes and backslashes in the output to help write shell scripts. For example:
-R
$ oki -R rizin -u 'r:/usr/local/lib/librz_util.so.0.7' \ -u 'r:/usr/lib/libm.so.10.1' \ -u 'r:/usr/lib/libutil.so.17.0' \ (...)
It would be nice if we could make this behavior optional so it does this instead:
$ oki -R rizin -u r:/usr/local/lib/librz_util.so.0.7 -u r:/usr/lib/libm.so.10.1 -u r:/usr/lib/libutil.so.17.0 (...)
The latter format makes it easier to create shared config files that can be used in multiple shell scripts. For example:
#!/bin/sh set -u work_dir="${OKI_WORKDIR:-${HOME}/memla}" oki \ -p stdio \ (...) -u rwc:/tmp \ -u r:/usr/libexec/ld.so \ -u r:/usr/lib \ -u r:/usr/lib/libc.so.97.0 \ $(/bin/cat /tmp/rules-example.txt) \ -- rizin $@
... where /tmp/rules-example.txt contains:
/tmp/rules-example.txt
-u r:/usr/local/lib/librz_util.so.0.7 -u r:/usr/lib/libm.so.10.1 -u r:/usr/lib/libutil.so.17.0 (...)
Perhaps this can even be the default behavior and the current behavior can be optional?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When parsing an ELF with
-R
, oki includes single quotes and backslashes in the output to help write shell scripts. For example:It would be nice if we could make this behavior optional so it does this instead:
The latter format makes it easier to create shared config files that can be used in multiple shell scripts. For example:
... where
/tmp/rules-example.txt
contains:Perhaps this can even be the default behavior and the current behavior can be optional?
The text was updated successfully, but these errors were encountered: