Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Project creation/file import fails silently with long project names, no path length validation before hitting Windows path limit

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
cpp

Línea de trabajo

Start by reproducing project creation and file import with the long names described, then trace the project and import paths associated with the logged filesystem failures. Done means validating the resulting Windows path before filesystem operations and presenting a clear, actionable error instead of a silent or low-level failure.

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

Descripción

Version and Platform (required):

  • Binary Ninja Version: 6.0.10474-dev Ultimate (c9ea4d90)
  • Edition: Ultimate
  • OS: Windows 11 Pro
  • OS Version: 10.0.26200 (Build 26200)
  • CPU Architecture: x64 (AMD64 Family 25 Model 97, running under QEMU/Proxmox virtualization)

Bug Description:
Binary Ninja does not validate the resulting file system path length when creating a project with a long project name. This can cause project creation or file import to fail with no clear indication to the user of why:

  • If the project name is around 250 characters, project creation itself fails.
  • If the project name is around 200 characters, the project is created successfully, but importing a file into the project fails.

The underlying cause may be related to the Windows path length limit (paths exceeding 250 characters generally cause errors on Windows), though this is a guess based on the character counts observed and has not been confirmed.

Steps To Reproduce:

  1. In Binary Ninja, start creating a new project
  2. Set the project name to a string approximately 250 characters long
  3. Attempt to create the project
  4. Observe that project creation fails (see log output below)
  5. Repeat with a project name approximately 200 characters long
  6. Observe that the project is created successfully
  7. Attempt to import a file into the project
  8. Observe that the file import fails (see log output below)

Expected Behavior:
Binary Ninja should validate project name/path length before attempting to create the project directory or copy files, and should give the user a clear, actionable error (e.g. "project name too long") rather than failing with a low-level filesystem error, or should otherwise handle long paths without failing.

Relevant log output:

[Default] copy_file: The system cannot find the path specified.: "C:/Users/vector35/Downloads/helloworld_thread.exe", "C:\Users\vector35\Downloads\12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.bnpr\data\9a\7f3cf5-984d-4d15-9357-a5b2bd5197e6"
[Projects] Failed creating project due to filesystem error: create_directories: The system cannot find the path specified.: "C:\Users\vector35\Downloads\1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.bnpr\"
[MainWindow] Failed to create project
[MainWindow] Checking for plugin updates...
[Default] copy_file: The system cannot find the path specified.: "C:/Users/vector35/Downloads/helloworld_thread.exe", "C:\Users\vector35\Downloads\12345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980123456798012345679801234567980.bnpr\data\34\70bf80-6783-41ed-bdcb-8ad4c9fec4d2"
Lenguaje dominante
C++
Estrellas
1.3k
Forks
298
Merge medio
4 d 13 h
PR fusionados (30 d)
20

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.