-
Notifications
You must be signed in to change notification settings - Fork 36
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
store additional metadata in INFO lines #502
Comments
Something like this would make it a lot easier to add APIs to the Mozilla Symbols Server to do things like "get all the symbols for build xyz". |
gabrielesvelto
added a commit
to gabrielesvelto/dump_syms
that referenced
this issue
Dec 15, 2023
gabrielesvelto
added a commit
that referenced
this issue
Dec 16, 2023
* Add an option to insert custom INFO lines into the output files This fixes issue #502
This is done, I just need to cut a new releases |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use
dump_syms
to extract symbol information from binaries for a specific build of some product. The symbol files are then uploaded to the symbol server. At that point, we have no way of knowing which build of what product generated this symbol information. It would be helpful to capture that at the timedump_syms
was run. This would help debugging symbol problems, indexing symbols for finding them later, etc.Maybe there's other information that would be helpful to capture as well? Maybe it's helpful to generalize the problem to "capture additional metadata at the time of symbol file creation and store as key/value pairs in INFO lines"?
Maybe something like:
Which would then result in a header something like this:
Or something like that.
The text was updated successfully, but these errors were encountered: