Indeed I think gemu_log() is the problem here.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828723
Title:
[RFE] option to suppress gemu_log() output
Status in QEMU:
New
Bug description:
Wit
Although arguably the line:
gemu_log("Unsupported setsockopt level=%d optname=%d\n", level,
optname);
Could be
qemu_log_mask(LOG_UNIMP,)
Not sure where gemu_log is used, it seems to be strace related.
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
The -d/-D options should work in linux-user as well. You can also set
QEMU_LOG_FILENAME and QEMU_LOG environment variables. Do these not work
for you?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/182
This series might be helpful:
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02067.html
** Tags added: linux-user
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828723
Title:
[RFE] optio
