Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ELF entrypoint not respected #2177

Closed
jackcmay opened this issue Dec 14, 2018 · 0 comments
Closed

ELF entrypoint not respected #2177

jackcmay opened this issue Dec 14, 2018 · 0 comments
Assignees
@jackcmay
Milestone
v0.12.0 Beacons

Comments

@jackcmay
Copy link
Contributor

Problem

Its assumed that a BPF program's entrypoint is the beginning of the .text section. The entrypoint could be anywhere in the .text section and with the introduction of multi-file projects are likely to not be.

Proposed Solution

  • Start program execution at the entrypoint listed in the ELF header
  • Explicitly pass the entrypoint symbol name to LLVM when building the ELF
@jackcmay jackcmay added this to the v0.12 Beacons milestone Dec 14, 2018
@jackcmay jackcmay self-assigned this Dec 14, 2018
This was referenced Dec 14, 2018
Closed
Merged
tao-stones pushed a commit to tao-stones/solana that referenced this issue Jul 25, 2024
@jstarry
refactor: new ExecutedTransaction struct to merge load and executio…
21fbec7 
…n details (solana-labs#2177)

* refactor: move loaded transaction into execution result

* refactor: return executed_tx from execute_loaded_transaction

* refactor: remove fee details from transaction details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jackcmay jackcmay

Labels
None yet
Projects
None yet
Milestone
v0.12.0 Beacons
Development

No branches or pull requests
1 participant
@jackcmay