Re: RFC strace via gdbserver

2017-02-03 Thread Stan Cox
I picked up Josh's work to support running strace over the gdb remote serial protocol. Josh's last message is quoted below. The gdb rsp support interfaces to gdbserver using the gdb rsp to run, attach, get registers, get memory, get syscall info - https://github.com:stanfordcox/strace.git - re

Re: RFC strace via gdbserver

2017-01-11 Thread Stan Cox
This is an example that shows the back and forth interaction that is possible between an strace aware gdbclient and the gdb remote protocol aware strace. STRACE client Process 10442 attached in non-stop mode GDB client (gdb) continue Thread 2 "tstthreads1.x" hit Breakpoint 3, thread_worker_2 ()

Re: RFC strace via gdbserver

2016-11-29 Thread Stan Cox
I just made one small change. I didn't want to start using the vContc;c:ppid.tid form until I saw the completed syscall where the tid changed. For recent linux this is typically set_robust_list. So once the syscall return is seen it starts using the pid.tid form. This was already there in a

Re: RFC strace via gdbserver

2016-11-09 Thread Stan Cox
> 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

Re: RFC strace via gdbserver

2016-11-09 Thread Josh Stone
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

Re: RFC strace via gdbserver

2016-11-09 Thread Stan Cox
> 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

Re: RFC strace via gdbserver

2016-11-09 Thread Josh Stone
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

Re: RFC strace via gdbserver

2016-11-02 Thread Stan Cox
> 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 Here is an interleaved example with two threads.

RFC strace via gdbserver

2016-10-12 Thread Stan Cox
This is a followup to https://sourceforge.net/p/strace/mailman/message/34782296/ which describes Josh Stone's work on strace support for the gdb remote protocol. https://github.com/cuviper/strace/ Initially this effort supported gdbserver "all stop" mechanism, which stops all threads. Suppo

Re: RFC strace via gdbserver

2016-04-17 Thread Josh Stone
On 04/17/2016 10:25 PM, Dmitry V. Levin wrote: >> Dmitry pointed out -P and -y path-based options before, which I haven't >> found a solution for. Technically /proc/pid/fd access will work just >> fine if the gdbserver is local anyway, but that's cheating, and can't be >> assumed in general. It m

Re: RFC strace via gdbserver

2016-04-17 Thread Dmitry V. Levin
Hi, On Fri, Apr 15, 2016 at 05:30:12PM -0700, Josh Stone wrote: > Hi folks, > > Just wanted to give an update on this project, running strace over the > gdbserver protocol. I've quoted my original message below, in case you > missed it the first time, and source is here: > https://github.com/c

Re: RFC strace via gdbserver

2016-04-15 Thread Josh Stone
Hi folks, Just wanted to give an update on this project, running strace over the gdbserver protocol. I've quoted my original message below, in case you missed it the first time, and source is here: https://github.com/cuviper/strace/ The code has been rebased onto a much newer development branc

Re: RFC strace via gdbserver

2016-01-24 Thread Dmitry V. Levin
Hi, On Wed, Jan 20, 2016 at 12:10:25PM -0800, Josh Stone wrote: > Hi, > > I've been experimenting with using strace via gdbserver, through the gdb > remote protocol. It's now in good enough state that I'd like to get > some feedback. > > First, syscall support in gdbserver is very new. There w

RFC strace via gdbserver

2016-01-20 Thread Josh Stone
Hi, I've been experimenting with using strace via gdbserver, through the gdb remote protocol. It's now in good enough state that I'd like to get some feedback. First, syscall support in gdbserver is very new. There was a patch posted a few years ago by Philippe Waroquiers, but I only just finis