| Re: [hatari-devel] Problems with trailing backslash in path names (was: Problems with files greater 2 GiB) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Problems with trailing backslash in path names (was: Problems with files greater 2 GiB)
- From: Andreas Grabher <andreas_g86@xxxxxxxxxx>
- Date: Tue, 8 Jul 2025 19:11:27 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; bh=qICtN/8UrKoSxXJxe3QIS4IKjUwsnqWZd5nBT6kPoQM=; h=From:Content-Type:Mime-Version:Subject:Date:To:Message-Id:x-icloud-hme; b=nAQ+YyCaOcQXyJhkEUYPVDHI88ohLQexpw/7oIsJwBGRBRI0awY5k8WhFdeDtzpNdQXdu5lDt3woVbkqWzYsjjhKluLTMUm7eXJLAO3un12nEOZuyGXE0wpb2iiXaO3y3KBO3RaOi45Or3ajKN2evZ21hHElrO+kf0bdf9zCMhlt+MKJN/kyzjNwR/7t2TVEyTblgWvQiR1vC7GbMjLnTJEmjGn7sOtg/1mDEPAD12JT1aSe+TJq+wAYinizz6UQEZWz10hEEem4xNvZKKYLqDe1kk35sSSEiyVk3TTva7PQJrKtBGMmFKqw6ydkKq77iRaenpILQ1pKg4RRujW0cQ==
> Am 29.06.2025 um 13:39 schrieb Thomas Huth <th.huth@xxxxxxxxx>:
>
> Am Sun, 29 Jun 2025 08:19:39 +0200
> schrieb Andreas Grabher <andreas_g86@xxxxxxxxxx>:
>
>> Large file support seems to work for Windows users. Thanks again!
>>
>> But there seems to be a new issue when enabling large file support: Some functions like stat() on Windows do no longer work with path names containing a trailing backslash. They did before enabling large file support. Do you experience the same on Hatari?
>
> So far I'm not aware of any complaints yet.
>
> Thomas
>
After more testing I can confirm that when enabling large file support on Windows there is a big problem with path strings ending with a backslash. Obviously stat() will reliably fail if the path parameter contains a trailing backslash. The backslash is interpreted as an escape character. This will for example cause File_DirExists() to fail. This is of course not the only failure.
I think this needs to be fixed in the GUI code (for some reason it adds trailing backslashes to all path strings). That should be done before the next release (2.6.1) as this is a severe bug.