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
A common use case is comparing the quality of decompilation output from different decompilers of the same function. I would like to add a new feature, "synchronized navigation," to the frontend. Once this feature is enabled, when a user navigates to inside a function in one of the decompiler panels, all other decompiler panels will also scroll to the beginning of that function. This feature should be enabled by default.
The text was updated successfully, but these errors were encountered:
Are you thinking this should be implemented as pure javascript in a best-effort way to track based on names or pattern matching? By separately producing a list of offsets and functions to be used independently to match navigation?
What about when tools produce different (but identically named) entries for PLT/GOT?
It'd be a great feature I'm just concerned there's a lot of edge cases. I guess as long as the failure case is just "it is the same as we have now" and doesn't result in weird/confusing/wrong things it can only be an improvement.
I’m thinking of a best-effort approach that’s implemented only in the frontend. When we switch to per-function output in the backend (as Kevin has suggested before), we can switch to a more accurate, maybe binary address-supported mapping.
A common use case is comparing the quality of decompilation output from different decompilers of the same function. I would like to add a new feature, "synchronized navigation," to the frontend. Once this feature is enabled, when a user navigates to inside a function in one of the decompiler panels, all other decompiler panels will also scroll to the beginning of that function. This feature should be enabled by default.
The text was updated successfully, but these errors were encountered: