> It's still not clear to me what it means to "follow" syscalls for :2.
> Is that copying the syscall watchlist to the child?
es the default?
It was an attempt to mimic this behavior by filtering the tids and
syscalls in gdb_catch_this_syscall_p.
/usr/bin/strace -f tstthreads.x
...
mprotect(0x7
On 11/09/2016 11:47 AM, Stan Cox wrote:
>
>> Can you explain your -f changes?
>>
>> I see you're alternating QCatchSyscalls:1 or QCatchSyscalls:2 -- what
>> are these values? Has this protocol change gone into gdb upstream, or
>> just your own gdb branch?
> Yes, it was just a local change. QCatc
> Can you explain your -f changes?
>
> I see you're alternating QCatchSyscalls:1 or QCatchSyscalls:2 -- what
> are these values? Has this protocol change gone into gdb upstream, or
> just your own gdb branch?
Yes, it was just a local change. QCatchSyscalls:1 was without -f being
specified and Q
On 11/02/2016 11:54 AM, Stan Cox wrote:
>
>> Additionally, support for qualifying expressions (-e expr) and following
>> children (-f) will be pushed soon.
> -f and -e support has been added to the gdbserver remote protocol backend in
> the strace branch at https://github.com:stanfordcox/strace
