hi Peter:
You are right, any additional modification should not affect the previous.
We expect that if this issue could be resolved without code change it's the
best.
it may need to modify both binfmt_misc side to pass more information for flag P
and qemu side to handle it.
--
You received this
hi Peter:
Thanks for your suggestion.
but anyway we have to modify qemu code when binfmt_misc passes argv[0] in,
right?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1818483
Title:
qemu user mode
Hi Sir:
During our test in chroot environment with qemu-user-static, we got some test
cases failed because of program output warning with unexpected full path name.
For example in test module "Devscripts"
the test item for broken tarball expected the warning info:
< tar: This does not look like a
I modified binfmt_misc.c to let it send one more args if the corresponding
binfmt_misc flags include "P", also I modified main.c in qemu as attached
patch_qemu_main.patch to check if the input args include such string. Then qemu
user could support both scenarios.
Is this modification feasible?
Public bug reported:
Hi Sir:
During our test in chroot environment with qemu-user-static, we got some test
cases failed because of program output warning with unexpected full path name.
For example in test module "Devscripts"
the test item for broken tarball expected the warning info:
but the ou
