The test

JvmtiExport::can_hotswap_or_post_breakpoint()

is used instead of

JvmtiExport::can_examine_or_deopt_anywhere()

in the following two places:

c1/c1_GraphBuilder.cpp --
        // Register dependence if JVMTI has either breakpoint
        // setting or hotswapping of methods capabilities since they may
        // cause deoptimization.
        if (JvmtiExport::can_hotswap_or_post_breakpoint() && !dependency_recorded) {
          add_dependent(actual_recv, inline_target);
        }
        return;


opto/parse1.cpp --
    // Always register dependence if JVMDI is enabled, because
    // either breakpoint setting or hotswapping of methods may
    // cause deoptimization.
    if (JvmtiExport::can_hotswap_or_post_breakpoint()) {
      C->recorder()->add_dependent(NULL, method());
    }

This could cause random behavior or crashes if only the monitor,
methed entry, etc. capabilities are used. The comments also,
clearly, need an update.
###@###.### 2004-02-24