Project creation/file import fails silently with long project names, no path length validation before hitting Windows path limit
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- cpp
- Ambito
- desktop, operating-systems
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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:
- In Binary Ninja, start creating a new project
- Set the project name to a string approximately 250 characters long
- Attempt to create the project
- Observe that project creation fails (see log output below)
- Repeat with a project name approximately 200 characters long
- Observe that the project is created successfully
- Attempt to import a file into the project
- 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"
- Lingua principale
- C++
- Stelle
- 1.3k
- Fork
- 298
- Merge medio
- 4g 13h
- PR unite (30g)
- 20
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Vector35/binaryninja-api
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
Vector35/binaryninja-api#8540 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
Vector35/binaryninja-api#8446 ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
Vector35/binaryninja-api#8444 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Vector35/binaryninja-api#8441 · 3 commenti ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Vector35/binaryninja-api#8404 ·
Tutte le issue di Vector35/binaryninja-api
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Apertacoarray
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·