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

TTY: clarify uses of "class id" versus "class pattern"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 1.4.2
    • 1.4.2
    • core-svc
    • None
    • mantis
    • generic
    • generic



      Name: tb29552 Date: 07/24/2002


      In the help output of jdb, we have:
       [...]
        <class id> or <exception-class id>: full class name with package
        qualifiers or a pattern with a leading or trailing wildcard ('*')
        NOTE: any wildcard pattern will be replaced by at most one full class
        name matching the pattern.
       [...]

      The only jdb commands that support this wildcarding are
      catch/ignore, and the implementation has flaws (bug ID 4671838).

      Other uses of <class id> will not work properly if a
      wildcard is present. This includes the following
      jdb commands:

        class <class id> -- show details of named class
        methods <class id> -- list a class's methods
        fields <class id> -- list a class's fields
        stop in <class id>.<method>[(argument_type,...)]
        stop at <class id>:<line> -- set a breakpoint at a line
        clear <class id>.<method>[(argument_type,...)]
        clear <class id>:<line> -- clear a breakpoint at a line
        watch [access|all] <class id>.<field name>
        unwatch [access|all] <class id>.<field name>
        redefine <class id> <class file name>

      ======================================================================

            tbell Tim Bell
            tbell Tim Bell
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: