diff options
author | Mattias Andrée <maandree@kth.se> | 2020-05-30 22:46:34 +0200 |
---|---|---|
committer | Mattias Andrée <maandree@kth.se> | 2020-05-30 22:46:34 +0200 |
commit | a9ae8c060f5050da8f5b5a830ab5be54bfb600fa (patch) | |
tree | a97265cec265fd557ef981a81e9402ea08528556 | |
parent | Continue vfork parent after child execs (diff) | |
download | sctrace-a9ae8c060f5050da8f5b5a830ab5be54bfb600fa.tar.gz sctrace-a9ae8c060f5050da8f5b5a830ab5be54bfb600fa.tar.bz2 sctrace-a9ae8c060f5050da8f5b5a830ab5be54bfb600fa.tar.xz |
Add todo about different (bad) behaviour under valgrind
Signed-off-by: Mattias Andrée <maandree@kth.se>
-rw-r--r-- | sctrace.c | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -140,6 +140,7 @@ main(int argc, char **argv) } /* exec will block until parent attaches */ execvp(*argv, &argv[with_argv0]); + /* TODO on failure, why does it get into a SIGSEGV loop under valgrind? */ eprintf("execvp %s:", *argv); default: orig_pid = pid; |