Public bug reported:
While running qemu user x86_64 x86 with gdb server, calling functions
are not working.
Here is how to reproduce it:
run in a terminal:
$ qemu-x86_64 -g 12345 -L / /bin/ls
In another terminal run gdb:
(gdb) file /bin/ls
(gdb) target remote :12345
(gdb) b _init
(gdb) c
(gdb)
Public bug reported:
Here is two simple steps to reproduce the bug:
$ qemu-x86_64 -E LD_PROFILE=libc.so.6 -E LD_PROFILE_OUTPUT=. -g 12345 -L
/ /bin/ls
(libc.so and /bin/ls might change on your system, in this case we just
need a binary with a profilable needed library)
In a other window
I will check that again, pretty sure I saw that.
Anyway any chance there is an option/fix for that?
Today it is impossible to differentiate strace output with program's stderr
output, and it is causing trouble while used in scripts.
--
You received this bug notification because you are a member
If this is not for strace, then why when I launch qemu as subprocess (example:
from a python script)
with option -strace -D it creates a log file called -strace? Seems
like a bug to me.
Anyway, I understand you don't want to break the current behavior, is there any
chance this gets added in
Public bug reported:
I have been trying to access qemu -strace output from a script
The main problem was it was on stderr, the strace output was merged with my
program's stderr output.
Then I tried to use the -D option, to log the output to a file.
This didn't work even if the log file was
