vosen/ZLUDA · error

Failed to read {}: {}

Error message

Failed to read {}: {}

What it means

zluda build-script panic in check_lfs_file: the DLL opened but reading its first 2 bytes failed, meaning the path is a directory, the file is empty, or an I/O error occurred. The subsequent MZ-header assert exists to catch LFS stubs; this earlier error means the file is unreadable before its contents can even be checked.

Source

Thrown at zluda/build.rs:27

        check_lfs_file(dll_path);
    }
    let git = Gix::builder().sha(false).build();
    Emitter::default()
        .add_instructions(&git)
        .unwrap()
        .emit()
        .unwrap();
}

fn check_lfs_file(bc_path: &str) {
    use std::fs::File;
    use std::io::Read;

    let mut magic = [0u8; 2];
    File::open(bc_path)
        .unwrap_or_else(|e| panic!("Failed to open {}: {}", bc_path, e))
        .read_exact(&mut magic)
        .unwrap_or_else(|e| panic!("Failed to read {}: {}", bc_path, e));
    assert!(
        &magic == b"MZ",
        "{} is a git lfs stub and not the actual file. Run `git lfs pull` to fetch it",
        bc_path
    );
}

View on GitHub (pinned to 9c8b43f242)

Solutions

1. Verify bin/nvcudart_hybrid64.dll is a non-empty regular file
2. Run `git lfs pull` to restore a possibly corrupted or empty smudge result
3. Check permissions and free disk space, then rebuild

When it happens

Trigger: Thrown at zluda/build.rs:27 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of vosen/ZLUDA@9c8b43f242 (2026-09-06). Data as JSON: /api/errors/8e65bb345edfbb25. Report an issue: GitHub.