This bug was fixed by commit aa07f5ecf9828 in 2014 and has been released
in QEMU.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Hi,
Is this patch deployed in new version of QEMU?
Thanks,
Maxim
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Status in QEMU:
New
B
Thanks. That version
Reviewed-by: Peter Maydell
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Status in QEMU:
New
Bug description:
Ok, fixed.
** Patch added: "qemu.patch"
https://bugs.launchpad.net/qemu/+bug/1299190/+attachment/4062748/+files/qemu.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access t
Some nits:
The "(CPUArchState *)" cast isn't necessary
We should use exec_path, not ts->bprm->argv[0] (the guest argv[0] isn't
necessarily the executable path)
We don't want to call path() here -- exec_path is a host path, and only guest
filename paths need to go through path().
Looking a lit
Yes, it works. Here is updated patch.
** Patch added: "qemu.patch"
https://bugs.launchpad.net/qemu/+bug/1299190/+attachment/4062345/+files/qemu.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
(I got the bracket placement wrong there so as you can tell the code is
untested :-))
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Statu
That patch will copy the whole of the target executable into a temporary file
without changing any of it -- the fake_open mechanism is really intended for
cases where we need to return modified results. Wouldn't it be easier to just
have something in do_open() that said:
if (is_proc_myself(p
Looks good, I'll get this to linux-user que once QEMU 2.0 is released.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1299190
Title:
Access to /proc/self/exe in linux-user mode
Status in QEMU:
Ne
I think the problem is not in libbacktrace per se but rather
libsanitizer initializing libbacktrace with contents of /proc/self/exe.
Patch is still relevant though.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
This tiny patch seems to work.
** Patch added: "qemu.patch"
https://bugs.launchpad.net/qemu/+bug/1299190/+attachment/4055887/+files/qemu.patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/129919
11 matches
Mail list logo
