On Fri, Feb 10, 2017 at 9:20 PM, Al Gambardella wrote:
> I attached strace to a running process and I am trying to understand
> what strace is telling me regarding the select system call. Here are
> two lines of the strace output below:
>
> _newselect(17, NULL, NULL, [16], {0, 0}) = 0 (Timeout)
>
I attached strace to a running process and I am trying to understand
what strace is telling me regarding the select system call. Here are
two lines of the strace output below:
_newselect(17, NULL, NULL, [16], {0, 0}) = 0 (Timeout)
_newselect(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
Add a test: gdbrsp.c and a test driver gdbrsp.test. The test checks if
gdbserver is available and if it supports syscall catching.
diff --git a/tests/Makefile.am b/../src/tests/Makefile.am
index 90b7bf3..2c059e4 100644
--- a/tests/Makefile.am
+++ b/../src/tests/Makefile.am
@@ -143,7 +143,6 @@
The gdbserver directory contains the gdbserver backend, which
communicates with gdbserver via the gdb remote protocol, e.g.
strace sends packet: $vCont;c (continue)
strace receives packet:
T05syscall_entry:16;06:b0e2ff7f;07:68e2ff7f;10:27a9b0f7ff7f;thread:p2162.2162;core:
Requesting comments on this patch, which adds support for the gdb
remote serial protocol, which is described further in "info gdb
'Remote Protocol' 'Packets'" This protocol connects to gdbserver,
which catches the syscalls and returns information about them, as well
as register and memory info, via
