🐛 Bug: BreakPoints fallback shows original developer's local hard drive paths to all users

[Jayant-kernel]

🐛 Bug: BreakPoints fallback shows original developer's local hard drive paths to all users

Description

In webapp/src/components/GdbComponents/BreakPoints/BreakPoints.jsx, the component defines a fallback data array containing the original developer's local absolute file paths:

const data = [
  {
    offset: "0x2fffa36f603112ffff34",
    addr: "/Users/shubh/lib/node_modules/@stdlib/math/docs/t.js:18",
  },
  ...
];

Because of the render logic (infoBreakpointData ? infoBreakpointData : data?.length > 0 ? data.map(...)), if the user hasn't set any breakpoints yet or the backend response is empty, the UI exposes these 4 hardcoded shubh directory paths. This exposes internal developer environments and is highly confusing to the user.

• ---

Expected behaviour

The BreakPoints.jsx component should exclusively render actual breakpoint data fetched from info_breakpoints. If no breakpoints exist, it should render nothing (or an empty state message), rather than defaulting to hardcoded mock data.

To Reproduce

1. Navigate to the /debug route on a fresh instance.
2. Observe the BreakPoints box on the right side of the screen.
3. Because the backend has not yet pushed live breakpoint data, the UI will loop through the static array and render the 4 fake /Users/shubh/... paths directly to the screen.

• ---

Suggested Fix

Modify webapp/src/components/GdbComponents/BreakPoints/BreakPoints.jsx to delete the const data = [...] declaration array and strip the fallback ternary logic out of the return block.