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

Analysing CGO libraries #19

Open
ayuhito opened this issue May 4, 2024 · 1 comment
Open

Analysing CGO libraries #19

ayuhito opened this issue May 4, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@ayuhito
Copy link

ayuhito commented May 4, 2024

Not sure if this is possible, but maybe it would be a useful feature to be able to analyze CGO libraries and their footprint? e.g. I'm using https://github.com/mattn/go-sqlite3 and https://github.com/marcboeker/go-duckdb which leads to a very large obscure 30MB .text section that doesn't really tell me much.

Thank you for this project! It's helped me a lot!

@Zxilly
Copy link
Owner

Zxilly commented May 4, 2024

It's possible after the dwarf analysis be implemented. Currently any cgo dependencies will be ignored.

@Zxilly Zxilly added the enhancement New feature or request label May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants