You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd also think we should strongly consider implementing debuginfod support (Support debuginfod #203), as such support could represent a very convincing building block for others
do we need an ElfData symbol source, similar to the existing GsymData?
At this point it's not clear whether *1 or *2 requires any backwards compatibility breaking changes, so neither may end up being a blocker, but we need clarity on this front first. And, perhaps, even if those changes are not breaking, we may still want to consider them blockers to have a fully-featured API to show for.
For item *2 we will have said clarity once the prototype is extended to support process symbolization programmable dispatch. For *1, we need to work on a prototype first that illustrates API requirements.
The text was updated successfully, but these errors were encountered:
do we need an ElfData symbol source, similar to the existing GsymData?
I think we may want that eventually, but didn't include that in #634. Let's wait for an actual use case for this. Until then, I consider this a non-issue.
Tracking issue for the release of version
0.2
: the first stable0.2
version. I see two things lacking:Elf
andGsym
)debuginfod
support (Supportdebuginfod
#203), as such support could represent a very convincing building block for othersdo we need anElfData
symbol source, similar to the existingGsymData
?At this point it's not clear whether *1 or *2 requires any backwards compatibility breaking changes, so neither may end up being a blocker, but we need clarity on this front first. And, perhaps, even if those changes are not breaking, we may still want to consider them blockers to have a fully-featured API to show for.
For item *2 we will have said clarity once the prototype is extended to support process symbolization programmable dispatch. For *1, we need to work on a prototype first that illustrates API requirements.
The text was updated successfully, but these errors were encountered: