Bug: Terminal Silently Drops Consecutive Duplicate Commands

[Jayant-kernel]

Describe the bug

When using the debug control buttons (e.g., clicking "Next" or "Step" twice in a row), the second click is completely ignored by the terminal and backend.

Root Cause

In TerminalComp.jsx, the useEffect that triggers commands relies on toggling commandPress to run:

  useEffect(() => {
    if (terminalOutput) {
      defaultHandler(terminalOutput);
    }
  }, [commandPress]); 

However, since commandPress is a boolean toggle, if you click the SAME button multiple times, the state toggles back and forth. But because the terminalOutput is kept the same, and React batches the state update or fails to fire the effect appropriately, duplicate button clicks are dropped.

• ---

Expected behaviour

Clicking "Next" three times should execute the next GDB command three times.

To Reproduce

1. Start a debugging session.
2. Click the "Next" (arrow right) button in the DebugHeader.
3. The terminal executes next.
4. Click the same "Next" button again.
5. Bug: Nothing happens. The command is ignored.

• ---

Suggested Fix

Refactor the global state to replace the boolean toggle commandPress with an incrementing counter (e.g., setCommandCount(prev => prev + 1)) so the dependency array always sees a new, unique value on every click.

[Rasesh2005]

Can I work on this?

[Jayant-kernel]

@Rasesh2005
I am already working on it

[Jayant-kernel]

Hello @Shubh942! The backend URL was hardcoded across multiple frontend components, making it impossible to run the UI against an external backend (e.g. from Docker or a hosted environment). I have opened a pull request (#111) that replaces all instances of http://127.0.0.1:10000 with the VITE_BACKEND_URL environment variable, falling back to localhost by default. Everything is strictly human-written and follows contribution guidelines! I would love to be assigned to this issue so the PR can be reviewed and merged.