-
Notifications
You must be signed in to change notification settings - Fork 26
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
purl2dwarf: Get DWARFs from a PURL #260
Comments
As a package can contain multiple binaries I guess that the result would be a list of "DWARF information per binary"? |
Yes, that's per binary file |
What would this look like for a package like coreutils (with ~100 binaries)? |
more or less like this: - files:
- path: foo/bar/find
dwarf_paths:
- /home/joe/coreutil/includes/baz.h
- /home/joe/coreutil/find.c
- path: foo/bar/ls
dwarf_paths:
- /home/joe/coreutil/includes/baz.h
- /home/joe/coreutil/js.c |
It should be an add-on pipeline in the data model, it should be used for d2d on elfs. This part is just to collect dwarfs. |
The basis would be provided by the https://github.com/nexb/elf-inspector |
Will be closed by aboutcode-org/scancode.io#1068 |
Now we have an add-on pipeline in scancode.io to get dwarfs from a codebase, but we need this support for a package URL, so some of the ways we could achieve this, we can check if there is a download URL associated with that purl in qualifiers. If there is no download URL, we can try to get it from purlDB, and if there is nothing in purldb regarding that purl, get it from purl2url module from purl. |
@TG1999 you should sync up with @keshav-space on this #260 (comment) as he has some things in the works for purl2sym |
A good example of a package with DWARFs is https://repo1.maven.org/maven2/com/sun/jna/jna/3.0.9/jna-3.0.9.jar which has the PURL: |
Related is this issue: aboutcode-org/scancode.io#1121 Another example |
This is done. We now have: a pipeline
To test this feature:
And to test this first part of purl2dwarf, install the latest scancode.io
|
Create a PURL a service backed by new SCIO analysis pipelines that takes a PURL for a native binary package as an input, and returns the DWARF debug symbol compilation unit paths when available. This will specifically be worked out for Debian native binary packages.
The text was updated successfully, but these errors were encountered: