Re: [PATCH v2] linux-user/strace: Improve strace output for read() and getcwd()

2019-11-26 Thread Aleksandar Markovic
On Sun, Nov 24, 2019 at 12:56 PM Helge Deller wrote: > > The strace functionality in qemu-user lacks the possibility to trace > which real values get returned to pointers in userspace by syscalls. > > For example, the read() and getcwd() syscalls currently only show the > destination address where

Re: [PATCH v2] linux-user/strace: Improve strace output for read() and getcwd()

2019-11-25 Thread Helge Deller
On 24.11.19 13:38, no-re...@patchew.org wrote: > Patchew URL: https://patchew.org/QEMU/20191124115656.ga23...@ls3530.fritz.box/ > ... > This series seems to have some coding style problems. See output below for > more information: > > Subject: [PATCH v2] linux-user/strace: Imp

Re: [PATCH v2] linux-user/strace: Improve strace output for read() and getcwd()

2019-11-24 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20191124115656.ga23...@ls3530.fritz.box/ Hi, This series seems to have some coding style problems. See output below for more information: Subject: [PATCH v2] linux-user/strace: Improve strace output for read() and getcwd() Type: series Message-id

[PATCH v2] linux-user/strace: Improve strace output for read() and getcwd()

2019-11-24 Thread Helge Deller
The strace functionality in qemu-user lacks the possibility to trace which real values get returned to pointers in userspace by syscalls. For example, the read() and getcwd() syscalls currently only show the destination address where the syscalls should put the return values: 2532 read(3,0xff80038