search for: test_signal

...shell. So it is this shell that catches the signal resulting in it: > - dying and leaving zombies > - dying and taking its child with him (SIGHUP and SIGKILL) > - ignoring the signal (SIGINT, SIGTERM, SIGQUIT). > > Example of ID?s when I connect to a server and launch the script test_signal.sh : > PID PPID PGID SID > 4060 1598 4060 1556 sshd sshd: root at pts/2 > 4062 4060 4062 4062 bash -bash > 4075 4062 4075 4062 sh sh test_signal.sh > 4076 4075 4075 4062 sh sh test_signal.sh > > So in order...

Hi, >>> It would be nice to know what the precise technical issues are that have >>> prevented support for this from being added. From what I recall, it >>> seemed like the delay was largely due to details of the client >>> behaviour, and possibly some feature creep. It would indeed be really great to have some details on this point. Concerning the test of

...* Send the SIGSEGV signal. This initiates JIT compilation of sigsegv_handler */ kill (getpid (), SIGSEGV); /* When the timer finally fires, assuming sigsegv_handler is still compiling, LLVM crashes */ for (;;); return 0; } ============================= /scratch/sym/test_cases/test_signal> lli -force-interpreter main.bc sigsegv_handler: 0x9b02480 0 lli 0x08741d2e Segmentation fault /scratch/sym/test_cases/test_signal> lli main.bc sigsegv_handler: 0xf16ff8 Uh oh

...standard. Eric Wong (26): cleanup: avoid redundant error checks for fstat test_helper: connect(2) may fail with EINVAL GNUmakefile: fix non-portable tar(1) usage tests: provide a pure Ruby setsid(8) equivalent more portable symlink awareness for START_CTX[:cwd] test_signals: avoid portability issues with fchmod(2) cleanup error handling and make it less noisy Do not override Dir.chdir in config files configurator: add "working_directory" directive configurator: working_directory is expanded configurator: set ENV["PWD"...