Skip to content

Conversation

@procdump
Copy link

@procdump procdump commented Nov 27, 2025

Problem

Currently on each program execution the SBPF debugger starts listening on $VM_DEBUG_PORT.
This is particularly a problem when there are CPIs as on each CPI another VM is instantiated attempting to reuse $VM_DEBUG_PORT.

Summary of Changes

The VM's debug port is added an offset with regards to the CPI level to avoid port collisions.

This PR wraps up everything explained here anza-xyz/sbpf#79 but I believe with a simpler and cleaner implementation.

…fset

with regards to the CPI level to avoid port collisions. The reason for
this is that when debugging a CPI it needs another debug port to listen
on as it takes place in the middle of the ongoing TCP debugging session.
@mergify mergify bot requested a review from a team November 27, 2025 11:13
@mergify
Copy link

mergify bot commented Nov 27, 2025

The Firedancer team maintains a line-for-line reimplementation of the
native programs, and until native programs are moved to BPF, those
implementations must exactly match their Agave counterparts.
If this PR represents a change to a native program implementation (not
tests), please include a reviewer from the Firedancer team. And please
keep refactors to a minimum.

@procdump procdump marked this pull request as ready for review November 27, 2025 11:17
@procdump procdump requested a review from a team as a code owner November 27, 2025 11:17
@procdump
Copy link
Author

@Lichtso, @LucasSte can you have a look and share your opinion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant