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
mstange opened this issue
Nov 21, 2016
· 3 comments
Labels
featureWork that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXhebmarkersAnything to do with marker data structures, marker chart, or the marker table
The text was updated successfully, but these errors were encountered:
gregtatum
added
feature
Work that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXheb
markers
Anything to do with marker data structures, marker chart, or the marker table
labels
Mar 8, 2017
It's still not implemented. We also don't show callstacks from inside markers anywhere at the moment. E.g. if you find a "Styles" marker in the markers tab, you'll see that it has a disclosure triangle, but clicking it won't do anything. The old cleopatra would show the marker's call stack under there.
Heh, it seems I was confused about how stacks inside markers are represented when I filed this issue. They don't come with their own stack table, they share the stack table with the thread that contains the marker. And that stack table was already being symbolicated. So the symbolication part was never an issue. There was only the issue that we weren't displaying the stack, but this has now been fixed in #756.
featureWork that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXhebmarkersAnything to do with marker data structures, marker chart, or the marker table
No description provided.
The text was updated successfully, but these errors were encountered: