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

C API for interfacing with traces? #587

Open
danielocfb opened this issue Apr 2, 2024 · 0 comments · May be fixed by #901
Open

C API for interfacing with traces? #587

danielocfb opened this issue Apr 2, 2024 · 0 comments · May be fixed by #901
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@danielocfb
Copy link
Collaborator

We could consider adding an API to blazesym-c for capturing traces emitted by the main crate. That could help with understanding of problems when even blaze_err is not sufficient.

I would think that most likely that will take a form similar to https://docs.rs/libbpf-rs/latest/libbpf_rs/fn.set_print.html, which allows users to set a function to be invoked for each "event".
@danielocfb danielocfb added enhancement New feature or request help wanted Extra attention is needed labels Apr 2, 2024
@danielocfb danielocfb mentioned this issue Nov 12, 2024
Open
danielocfb pushed a commit to d-e-s-o/blazesym that referenced this issue Nov 12, 2024
@d-e-s-o
capi: Add support for capturing traces
619209c 
The main Rust crate allows for configuration of the generic tracing
infrastructure to glean some insights into what is going on. So far the
C library didn't have any mechanism for tapping into that.
This change adds such infrastructure with the new blaze_trace()
function, which allows for registration of a callback function that is
invoked for each emitted trace line.

Closes: libbpf#587

Signed-off-by: Daniel Müller <[email protected]>
danielocfb pushed a commit to d-e-s-o/blazesym that referenced this issue Nov 12, 2024
@d-e-s-o
capi: Add support for tapping into traces
337597a 
The main Rust crate allows for configuration of the generic tracing
infrastructure to glean some insights into what is going on. So far the
C library didn't have any mechanism for tapping into that.
This change adds such infrastructure with the new blaze_trace()
function, which allows for registration of a callback function that is
invoked for each emitted trace line. It is intended to be used to better
understand what is going on.

Closes: libbpf#587

Signed-off-by: Daniel Müller <[email protected]>
@danielocfb danielocfb linked a pull request Nov 12, 2024 that will close this issue
Open
danielocfb pushed a commit to d-e-s-o/blazesym that referenced this issue Nov 12, 2024
@d-e-s-o
capi: Add support for tapping into traces
7ab983b 
The main Rust crate allows for configuration of the generic tracing
infrastructure to glean some insights into what is going on. So far the
C library didn't have any mechanism for tapping into that.
This change adds such infrastructure with the new blaze_trace()
function, which allows for registration of a callback function that is
invoked for each emitted trace line. It is intended to be used to better
understand what is going on.

Closes: libbpf#587

Signed-off-by: Daniel Müller <[email protected]>
danielocfb pushed a commit to d-e-s-o/blazesym that referenced this issue Nov 12, 2024
@d-e-s-o
capi: Add support for tapping into traces
c7d3a5a 
The main Rust crate allows for configuration of the generic tracing
infrastructure to glean some insights into what is going on. So far the
C library didn't have any mechanism for tapping into that.
This change adds such infrastructure with the new blaze_trace()
function, which allows for registration of a callback function that is
invoked for each emitted trace line. It is intended to be used to better
understand what is going on.

Closes: libbpf#587

Signed-off-by: Daniel Müller <[email protected]>
danielocfb pushed a commit to d-e-s-o/blazesym that referenced this issue Nov 12, 2024
@d-e-s-o
capi: Add support for tapping into traces
3e15d9e 
The main Rust crate allows for configuration of the generic tracing
infrastructure to glean some insights into what is going on. So far the
C library didn't have any mechanism for tapping into that.
This change adds such infrastructure with the new blaze_trace()
function, which allows for registration of a callback function that is
invoked for each emitted trace line. It is intended to be used to better
understand what is going on.

Closes: libbpf#587

Signed-off-by: Daniel Müller <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

capi: Add support for tapping into traces d-e-s-o/blazesym
1 participant
@danielocfb