5cdf6a132b
In my last change I made sure that the signal as reported from a truss exit is the same as if truss wasn't between parent and trussed program. I was smart enough to not have it coredump on SIGQUIT but it didn't ocur to me SIGSEGV might cause a coredump, too :-) So get rid of SIGQUIT extra hack and limit coredumpsize to zero instead. Tested: still works, correct signal reported. No more codedumps from SIGSEGV in the trussed proces. This file compiles cleanly on AMD64 (sledge). PR: Submitted by: Reviewed by: Approved by: Obtained from: MFC after: |
||
---|---|---|
.. | ||
alpha-fbsd.c | ||
amd64-fbsd32.c | ||
amd64-linux32.c | ||
extern.h | ||
i386-fbsd.c | ||
i386-linux.c | ||
i386.conf | ||
i386linux.conf | ||
ia64-fbsd.c | ||
main.c | ||
Makefile | ||
setup.c | ||
sparc64-fbsd.c | ||
syscall.h | ||
syscalls.c | ||
truss.1 | ||
truss.h |