-
-
Notifications
You must be signed in to change notification settings - Fork 323
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
Stdout from launcher processes doesn't get redirected to stdout_file provided #2111
Comments
I can't reproduce it even with your reproducer. /tmp/stdout.log does exist for me
are you sure you didn't export LIBAFL_DEBUG_OUTPUT? |
Hmm, this is unfortunate. I verified that |
i don't know. then you see where these guys points to |
For example, if I run the exact same code that you pasted.
|
And the subprocesses also point to |
I think I've found the issue: My [dependencies]
libafl = { path = "../LibAFL/libafl/", default-features = false, features = [
"prelude",
] }
libafl_bolts = { path = "../LibAFL/libafl_bolts/"}
libafl_qemu = { path = "../LibAFL/libafl_qemu/", features = [
"arm",
"systemmode",
], default-features = false } so I'm getting this LibAFL/libafl/src/events/launcher.rs Lines 326 to 437 in b231803
where the whole redirect thing doesn't get set up. Is this only supported when using the forking launcher? |
Sorry for not including the |
that's the problem |
Should I open a PR to hide the fields if the wrong feature is selected? This way they can't be set when they don't actually do anything? |
yes! please 👍 |
discovered while debugging AFLplusplus#2111
discovered while debugging AFLplusplus#2111
discovered while debugging AFLplusplus#2111
* fix(launcher.rs): hide file output behind appropriate feature flag discovered while debugging #2111 * fix(launcher.rs): implement stdout/stderr piping for non-forking unix * hide all accesses to stdout_file in cfg blocks * Conditionally add stdout_file config in frida_gdiplus
Reported on abcb2bf
Describe the bug
I'm not 100% sure this is a bug, but if it isn't this is a documentation issue. The documentation for
stdout_file
states:To Reproduce
Steps to reproduce the behavior:
stdout_file
onLaucherBuilder
run_client
write to stdoutstdout_file
doesn't existExpected behavior
I'd expect the file to be created and contain all the output from all
run_client
instancesAdditional context
Reproducer WARNING: THIS MIGHT WRITE TO
/tmp/stdout.log
(if it works for you):The text was updated successfully, but these errors were encountered: