Skip to content
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

WARP Created System Types Swamp the Types View Interface #6405

Open
utkonos opened this issue Feb 8, 2025 · 1 comment
Open

WARP Created System Types Swamp the Types View Interface #6405

utkonos opened this issue Feb 8, 2025 · 1 comment
Assignees
Labels
Component: WARP Effort: Trivial Issue should take < 1 day Impact: Low Issue is a papercut or has a good, supported workaround
Milestone

Comments

@utkonos
Copy link
Contributor

utkonos commented Feb 8, 2025

Version and Platform (required):

  • Binary Ninja Version: 4.2.6455
  • OS: macOS
  • OS Version: 15.3
  • CPU Architecture: x64

Bug Description:
System types from WARP block the viewing of the types with human readable names.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open a file that you know will have lots and lots of system types created by WARP.
  2. Expand the system types entry in any of the Types views

Expected Behavior:
Maybe file them somewhere else or prefix with a character that moves them out of the way?

Screenshots/Video Recording:

Image

Additional Information:
These don't appear to contain much information that the end user would really want to look at unless they were debugging something in WARP. And the name of the type is not human readable eather, just a UUID.

This may be deemed a feature request, but I thought I'd try ;)

@emesare emesare self-assigned this Feb 8, 2025
@emesare emesare added Impact: Low Issue is a papercut or has a good, supported workaround Effort: Trivial Issue should take < 1 day Component: WARP labels Feb 8, 2025
@emesare emesare added this to the Gallifrey milestone Feb 8, 2025
@emesare
Copy link
Member

emesare commented Feb 8, 2025

This particular issue should be resolved soon on https://github.com/Vector35/binaryninja-api/tree/test_warp_next

I had originally thought that only a subset of the types resolved were going to be unnamed but it appears that there was quite a few that weren't, might be related to the type itself not being correctly added to the WARP file as well.

@plafosse plafosse modified the milestones: Gallifrey, H Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: WARP Effort: Trivial Issue should take < 1 day Impact: Low Issue is a papercut or has a good, supported workaround
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants