Interface DebuggerListener


public interface DebuggerListener
Listener interface for receiving debugger events from the Qute debugger.

Implementations of this interface are notified when key events occur during a debugging session, such as output being produced, threads being started or stopped, execution being paused, or the debugger terminating.

This is typically used by the UI layer or other components that need to react to changes in the debugging state.

  • Method Summary

    Modifier and Type
    Method
    Description
    void
    Called when the debuggee execution is stopped, usually due to hitting a breakpoint, completing a step operation, or encountering an exception.
    void
    Called when the debugger session terminates completely.
    void
    Called when the state of a thread changes, such as when a thread is started or exited.
    void
    output(org.eclipse.lsp4j.debug.OutputEventArguments args)
    Called when the debuggee produces output.
  • Method Details

    • output

      void output(org.eclipse.lsp4j.debug.OutputEventArguments args)
      Called when the debuggee produces output.

      This is typically used to display logs, console messages, or any other textual output generated during the debugging session.

      Parameters:
      args - the OutputEventArguments containing the output details, such as the output text and category (e.g., stdout, stderr)
    • onThreadChanged

      void onThreadChanged(ThreadEvent event)
      Called when the state of a thread changes, such as when a thread is started or exited.
      Parameters:
      event - the ThreadEvent representing the change in thread state
    • onStopped

      void onStopped(StoppedEvent event)
      Called when the debuggee execution is stopped, usually due to hitting a breakpoint, completing a step operation, or encountering an exception.
      Parameters:
      event - the StoppedEvent containing details about why the execution stopped
    • onTerminate

      void onTerminate()
      Called when the debugger session terminates completely.

      After this method is invoked, no further events will be sent to the listener. Implementations can use this callback to clean up resources or update the UI to reflect the end of the debugging session.