JetBrains/intellij-community · error · EvaluateException

Debug info might be corrupt: {0}

Error message

Debug info might be corrupt: {0}

What it means

Error "Debug info might be corrupt: {0}" thrown in JetBrains/intellij-community.

Source

Thrown at java/debugger/impl/src/com/intellij/debugger/jdi/StackFrameProxyImpl.java:435

        if (values.containsKey(variable)) {
          return values.get(variable);
        }
        else {
          return getSingleValue(variable);
        }
      }
      catch (InvalidStackFrameException e) {
        error = e;
        clearCaches();
      }
      catch (InconsistentDebugInfoException ignored) {
        clearCaches();
        throw EvaluateExceptionUtil.INCONSISTEND_DEBUG_INFO;
      }
      catch (InternalException e) {
        if (e.errorCode() == JvmtiError.INVALID_SLOT || e.errorCode() == JvmtiError.ABSENT_INFORMATION) {
          throw new EvaluateException(JavaDebuggerBundle.message("error.corrupt.debug.info", e.getMessage()), e);
        }
        else {
          throw e;
        }
      }
      catch (Exception e) {
        if (!getVirtualMachine().canBeModified()) { // do not care in read only vms
          LOG.debug(e);
          throw new EvaluateException("Debug data corrupted");
        }
        else {
          throw e;
        }
      }
    }
    throw new EvaluateException(error.getMessage(), error);
  }

View on GitHub (pinned to be881553f2)

Solutions

1. Rebuild the class files so debug information is regenerated consistently.
2. Restart the debug session after a clean rebuild.

Example fix

Build | Rebuild Project, then rerun under the debugger.

When it happens

Trigger: The JDI reports local variable data that is inconsistent with the current stack frame.

Common situations: Corrupted or mismatched debug metadata, e.g. after recompilation during an active session or bytecode post-processing.

AI-assisted analysis of JetBrains/intellij-community@be881553f2 (2026-08-14). Data as JSON: /api/errors/199218898850d8b3. Report an issue: GitHub.