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.

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

Inner instruction reporting is confusing because they are collapsed within outer instructions #19467

Closed
jackcmay opened this issue Aug 27, 2021 · 0 comments
Labels
runtime Issues related to runtime, BPF, and LLVM stale [bot only] Added to stale content; results in auto-close after a week.

Comments

@jackcmay
Copy link
Contributor

Problem

A list of inner instructions is reported for each outer instruction within a transaction. This list only contains the instructions called but does not contain any information about who called them. This can be confusing because consumers have no direct way to distinguish between the two following cases:

A -> B -> C

and

A -> B, A -> C

Where A is the outer instruction and B and C are inners.

Information is available in the transaction log messages that could be parsed to determine this but that is far from ideal.

Proposed Solution

The inner-instruction list could contain associated stack depths for each inner instruction.

@pgarg66 pgarg66 added the runtime Issues related to runtime, BPF, and LLVM label Oct 26, 2022
@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Oct 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
runtime Issues related to runtime, BPF, and LLVM stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

2 participants