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

native signals aren't handled as specified

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 6
    • 6
    • hotspot
    • b81
    • generic
    • generic

      Documentation sources:
      1.Signal chaining
      http://java.sun.com/j2se/1.5.0/docs/guide/vm/signal-chaining.html
      2.Tiger trouble shooting
      http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf

      Documentation is incomplete. Trouble shooting guide has more info. I think information about signal handling should be clarified and moved on different page from 2.

      Signal handling issues:

      0. Solaris-sparc 10
      All works as specified.

      1. Linux-i686 (SUSE 9.2)
      1.1 Doc(2) have misprinted “_JAVA_SR_SIGNUM” as “_JAVA_SR_SIGNNUM”
      1.2 Doc(2) seems to confuse SIGUSR2 and SIGUSR1. SIGUSR1 handling works fine, but SIGUSR2 have many problems despite stated document assumption “SIGUSR2 unused on linux”.
      1.3 JVM prevents use of SIGCONT (18) in some scenarios. But documentation says nothing about it.

      2. Solaris-sparc 9
      2.1 Despite use of -Xrs and -XX:+UseAltSigs signal handlers fails in scenarios related to SIGUSR1, SIGUSR2.

      3. Solaris-x86 10
      3.1 Despite use of -Xrs and -XX:+UseAltSigs signal handlers fails in scenarios related to SIGHUP, SIGINT, SIGQUIT, SIGTERM.

      I've attached sources i have used to investigate and reproduce signal failures.
      ###@###.### 2005-05-27 08:46:40 GMT

            acorn Karen Kinnear (Inactive)
            azhmursunw Anatoly Zhmur (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: