From: Mike F. <va...@ge...> - 2013-05-02 03:04:31
Attachments:
signature.asc
|
i imagine this has to do with the probing of new ptrace features, but it still seems wrong for the first two lines to be signal stuff when tracing any program: $ ./strace -eexecve /bin/true --- stopped by SIGSTOP --- --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- execve("/bin/true", ["/bin/true"], [/* 69 vars */]) = 0 +++ exited with 0 +++ -mike |
From: Dmitry V. L. <ld...@al...> - 2013-05-04 21:21:12
|
On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: > i imagine this has to do with the probing of new ptrace features, but it still > seems wrong for the first two lines to be signal stuff when tracing any program: > $ ./strace -eexecve /bin/true > --- stopped by SIGSTOP --- > --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- These two lines are annoying, aren't they? It was discussed in February, with no visible result so far. > execve("/bin/true", ["/bin/true"], [/* 69 vars */]) = 0 > +++ exited with 0 +++ -- ldv |
From: Denys V. <dvl...@re...> - 2013-05-13 15:04:53
|
On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: > On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: >> i imagine this has to do with the probing of new ptrace features, but it still >> seems wrong for the first two lines to be signal stuff when tracing any program: >> $ ./strace -eexecve /bin/true >> --- stopped by SIGSTOP --- >> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- > > These two lines are annoying, aren't they? > It was discussed in February, with no visible result so far. I will try to suppress them. |
From: Dmitry V. L. <ld...@al...> - 2013-05-13 15:09:05
|
On Mon, May 13, 2013 at 05:04:36PM +0200, Denys Vlasenko wrote: > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: > > On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: > >> i imagine this has to do with the probing of new ptrace features, but it still > >> seems wrong for the first two lines to be signal stuff when tracing any program: > >> $ ./strace -eexecve /bin/true > >> --- stopped by SIGSTOP --- > >> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- > > > > These two lines are annoying, aren't they? > > It was discussed in February, with no visible result so far. > > I will try to suppress them. Another issue with USE_SEIZE is that -D option doesn't work: $ env -i ./strace -D /bin/true ./strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted Alarm clock -- ldv |
From: Dmitry V. L. <ld...@al...> - 2013-05-13 18:49:56
|
On Mon, May 13, 2013 at 07:08:57PM +0400, Dmitry V. Levin wrote: > On Mon, May 13, 2013 at 05:04:36PM +0200, Denys Vlasenko wrote: > > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: > > > On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: > > >> i imagine this has to do with the probing of new ptrace features, but it still > > >> seems wrong for the first two lines to be signal stuff when tracing any program: > > >> $ ./strace -eexecve /bin/true > > >> --- stopped by SIGSTOP --- > > >> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- > > > > > > These two lines are annoying, aren't they? > > > It was discussed in February, with no visible result so far. > > > > I will try to suppress them. > > Another issue with USE_SEIZE is that -D option doesn't work: > > $ env -i ./strace -D /bin/true > ./strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted > Alarm clock Apparently, this is due to CONFIG_SECURITY_YAMA in default configuration, it has nothing to do with PTRACE_SEIZE. I'm testing the fix. -- ldv |
From: Denys V. <dvl...@re...> - 2013-05-14 14:13:20
|
On 05/13/2013 05:04 PM, Denys Vlasenko wrote: > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: >> On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: >>> i imagine this has to do with the probing of new ptrace features, but it still >>> seems wrong for the first two lines to be signal stuff when tracing any program: >>> $ ./strace -eexecve /bin/true >>> --- stopped by SIGSTOP --- >>> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- >> >> These two lines are annoying, aren't they? >> It was discussed in February, with no visible result so far. > > I will try to suppress them. Ping me if this didn't (fully) fix it: commit 2a3d27552f17a5b378344620bec7d255bac65a8d Author: Denys Vlasenko <dvl...@re...> Date: Tue May 14 16:07:46 2013 +0200 Hide startup syscalls. Tested with "./strace [-D] [-q] [-bexecve] env true", all cases seem to work. * defs.h: Declare new variable: bool hide_log_until_execve. * strace.c: Define hide_log_until_execve. Rename skip_startup_execve to skip_one_b_execve. (startup_child): Do not set skip_one_b_execve = 1 here. (init): If "strace PROG" case (as opposed to "strace -pPID"), set skip_one_b_execve and hide_log_until_execve to 1. (trace): Don't print signal messages if hide_log_until_execve == 1. * syscall.c (trace_syscall_entering): Skip syscall printing if hide_log_until_execve == 1. Reset hide_log_until_execve if we enter execve syscall. (trace_syscall_exiting): Skip syscall printing if hide_log_until_execve == 1. |
From: Mike F. <va...@ge...> - 2013-05-14 17:13:46
Attachments:
signature.asc
|
On Tuesday 14 May 2013 10:13:12 Denys Vlasenko wrote: > On 05/13/2013 05:04 PM, Denys Vlasenko wrote: > > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: > >> On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: > >>> i imagine this has to do with the probing of new ptrace features, but > >>> it still seems wrong for the first two lines to be signal stuff when > >>> tracing any program: $ ./strace -eexecve /bin/true > >>> --- stopped by SIGSTOP --- > >>> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, > >>> si_uid=8282} --- > >> > >> These two lines are annoying, aren't they? > >> It was discussed in February, with no visible result so far. > > > > I will try to suppress them. > > Ping me if this didn't (fully) fix it: thanks, seems to look much nicer now -mike |
From: Dmitry V. L. <ld...@al...> - 2013-05-14 23:12:41
|
On Tue, May 14, 2013 at 04:13:12PM +0200, Denys Vlasenko wrote: > On 05/13/2013 05:04 PM, Denys Vlasenko wrote: > > On 05/04/2013 11:21 PM, Dmitry V. Levin wrote: > >> On Wed, May 01, 2013 at 11:04:13PM -0400, Mike Frysinger wrote: > >>> i imagine this has to do with the probing of new ptrace features, but it still > >>> seems wrong for the first two lines to be signal stuff when tracing any program: > >>> $ ./strace -eexecve /bin/true > >>> --- stopped by SIGSTOP --- > >>> --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=10908, si_uid=8282} --- > >> > >> These two lines are annoying, aren't they? > >> It was discussed in February, with no visible result so far. > > > > I will try to suppress them. > > Ping me if this didn't (fully) fix it: Thanks! On NOMMU systems, there is no way to catch the first execve call unless in -D mode, so these pre-execve messages cannot be reliably suppressed. I've applied a patch to address this NOMMU issue. -- ldv |