Use eBPF files for debugging instead of executable created from tests

[ERoydev]

What

• I have implemented a debugging workflow using agave-ledger-tool and solana-lldb to debug the eBPF compiled files directly.

• The previous approach relied on running a binary executable created with cargo test --no-run ..., which only allowed debugging in a Rust environment.

Why

• Our goal is to build a debugger that can debug Solana programs "on-chain"—that is, running on a local ledger—so we can inspect the actual deployed program behavior rather than just the Rust code.

• This approach provides a more accurate and realistic debugging experience, closer to production conditions.

Here is what is happening

User first starts his solana-local-validator
Then:

1. It will compile his program using cargo build-sbf --debug to create sBPF .so and .debug stripped files.
2. Run the compiled .so file on a local ledger using agave-ledger-tool in debug mode, starting a GDB remote server (usually on port 9001) for solana-lldb to attach and control execution.
3. Launch solana-lldb and attach it to that GDB remote port, loading the .debug file for debugging.

Now, the user can observe what is actually happening on-chain by reading the executed opcodes and instructions.

Limitations / Next steps:

• Currently supports only local ledger debugging using native solana programs.
• We need to figure it out how to map breakpoints to their compiled sBPF instructions