MacOS creates new windows from CLI

Abierto
#8,501 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, macos
Área
cli, desktop

Línea de trabajo

Start by reproducing the listed project-opening and binaryninja URL commands on macOS, including repeated opens, and compare the window and tab behavior with Windows or Linux. Trace the CLI and URL-handling entry points involved in those actions. Done means opening an existing or new project navigates predictably without unwanted windows, tabs, or reloads.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Version and Platform (required):

  • Binary Ninja Version: 6.0.1561
  • Edition: Ultimate
  • OS: MacOS
  • OS Version: 26 and 27
  • CPU Architecture: M3 Pro

Bug Description:
MacOS windows and tabs are not functioning correctly. Here is a couple of examples of behavior:

  1. Opening a project that hasn't been opened this session will cause the window to rapidly close and reopen to the project browser.

  2. Opening a project that has been opened this session will leave the first new tab openImage

  3. Opening a Binary Ninja URL from command line with open binaryninja:/.... will always make a new window, which does not happen on Windows or Linux.

  4. Open binaryninja:/bin/ls?expr=0x404da0+0n8 twice and observe that it makes a new tab of the same binary rather than navigating to a new one.

Image

Additional Information:
I think these are all connected bugs which is why I'm filing them together. If necessary we can break this up into sub-issues. I don't think it is a Qt problem, due to the CLI not working either.

Lenguaje dominante
C++
Estrellas
1.3k
Forks
298
Merge medio
5 d 5 h
PR fusionados (30 d)
19

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Vector35/binaryninja-api

Todos los issues de Vector35/binaryninja-api

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.