`std::io::fs::symlink` returns `IoError: OS Error 0` on windows

[klutzy]

fn main() {
    unsafe { ::std::rt::stack::record_sp_limit(0); } // #13259
    std::io::fs::symlink(&Path::new("testtest.c"), &Path::new("test.c")).unwrap();
}

task '<main>' failed at 'called `Result::unwrap()` on an `Err` value:
unknown error (OS Error 0: <locale-specific error message>)

It should return OS Error 1314 as described in #10264. Same symptom even if I call CreateSymbolicLinkW and GetLastError directly. However if I call them on custom #[start], I get the right error (1314).
Therefore this may be a sub-issue of #13259, but I'm a little unsure because the "workaround" does not work. Needs more investigation.

[klutzy]

(tested on windows 8.1 korean)

[retep998]

I just experienced a similar issue where MapViewOfFile was failing with ERROR_NOACCESS until I used a custom #[start].

[Felk]

I'm having the same error with a BufferedWriter.

fn main() {
    unsafe { ::std::rt::stack::record_sp_limit(0); }
    let file = File::open(&Path::new("test.txt"));
    let mut writer = BufferedWriter::new(file);
    println!("Flush: {}", writer.flush());
}

simply produces

Flush: Err(unknown error (OS Error 0: Der Vorgang wurde erfolgreich beendet.))
(= "the operation completet successfully.")

On Windows 7 (6.1.7601) german
rustc 0.11.0-pre-nightly

[alexcrichton]

I have a suspicion that d42cc13 may have fixed this. Could others test and see if it is indeed fixed?

[alexcrichton]

Closing, both of these are working as intended now (fixed by the commit I reference)