Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8357683

(process) SIGQUIT still blocked after JDK-8234262 with jdk.lang.Process.launchMechanism=FORK or VFORK

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • 25
    • 8, 25, 26
    • core-libs
    • linux, os_x, aix

      JDK-8234262 unblocks SIGQUIT for posix_spawn mode (the default), but it is still blocked for FORK and VFORK modes.

      Repro case JDK-8234262 is sufficient to show this: just execute `java/lang/ProcessBuilder/UnblockSignals.java` with `-Djdk.lang.Process.launchMechanism=FORK`.

      For FORK, we should also unblock the signal after the fork and before the exec.

      For VFORK, we should leave it that way - VFORK will be deprecated and removed soon, and changing the signal mask would influence the parent process.

            stuefe Thomas Stuefe
            stuefe Thomas Stuefe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: