This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: assertion "p >= path" failed
- From: Ken Brown <kbrown at cornell dot edu>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 11 Dec 2019 16:03:15 +0000
- Subject: Re: assertion "p >= path" failed
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cornell.edu; dmarc=pass action=none header.from=cornell.edu; dkim=pass header.d=cornell.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qXTm1tQuxb+xN5UD9l47w/vTZHQwXOt1zqK7d9SKBt8=; b=HIi9Gl0FDSqlBxojEYMcRc1S+xdGvmitvqoMK/02PFZ7235CkmOfWr7U7PFJhrCj7UpTU6s8lCIGJMidH0z8AcaNXw1rZcGCOIUeCTaDDSw4uO30QggwrYiiKCY12fvaunAiY5kcTpSlybS+bv11YfejFrx23kbLEeTL2HRHtVxsoTKjl0XuKEs7oQNyRxRbr4dGjzdxN0iBkszdUgAQZycEUwGfjvy0855iWbdQppxEpXt7qNsPuD9JOuBCu0LRllyKonNb7OZjrXnQVC5vanNsbizpMnjcbvIIaXKm3VxI5WM5zquy5JsEhwcrJrad/ABpqjjcbPTv/laLyZ5NYw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mHwTcBsWL3urm/8q/TIbXiYZvwTCbtqtyuqJxAOL8wm/wD2Toc7fzMsF+EosMcpiCZflJYK6S2UKqL/sKXkUVPX9GGpkIUDbVAmRy4oDJSEzw6XVaSfH//rxEvvUBWC0MmhZd43rGJvP9SZCt3oalk2PnZLP/nDapg36sVaHujc9F1grtSqZoOjENcloooryXBr43AccniLmQWovPYsFLKgU+1Bn+M3kExlMB7I2GD8aQMLKw1VNgwpGLGU/zBDpQ1G4tJqB3toOHKvT6F8x+8OK6LWpcegPvXKnPRhN0/nm7iU41jUhdv1eb/+7+MbP5EhFzC1jFZjAzV7VD2wDXg==
- References: <deaacaf0-81be-79fa-a2eb-1d30923cf89f@rl.ac.uk> <13b61476-6c41-1697-817e-652a695d3520@cornell.edu> <5b60cc71-fa1b-b972-10be-b37ff5756fab@rl.ac.uk> <46bc0b2e-a138-3e25-a403-4f3d6eff1651@rl.ac.uk> <f86de3f3-3a40-f189-8944-545b3c3aab57@cornell.edu> <ed566388-4dbc-30a3-a109-591c4b53bbd4@rl.ac.uk>
On 11/4/2019 7:49 AM, Tim Adye wrote:
> Hi Ken,
>
> On 31/10/2019 18:19, Ken Brown wrote:
>> [Please don't top-post on this list. Thanks.]
>>
>> On 10/30/2019 7:56 PM, Tim Adye wrote:
>>> I'm afraid I get a very similar error with 3.1.0-0.7:
>>>
>>> assertion "p >= path" failed: file
>>> "/home/kbrown/src/cygpackages/cygwin/cygwin-3.1.0-0.7.x86_64/src/newlib-cygwin/winsup/cygwin/path.cc",
>>>
>>> line 2906, function: int symlink_info::check(char*, const suffix_info*,
>>> fs_info&, path_conv_handle&)
>> OK, so your issue is different from the one that was fixed.
>>
>>> Again following resume from hibernation after going offline with the offline
>>> files as HOME (H:\).
>> I'm not familiar with offline files, so it would help if you would explain this
>> in complete detail.
>
> Offline Files is a feature of Sync Center that makes network files available to
> a user, even if the network connection to the server is unavailable. Windows
> keeps a copy of files stored on the network on the local computer. This allows
> users to work with them even when they are not connected to the network or a
> server is unavailable. The next time the user connects to the network or the
> server is available, their offline files on your computer will automatically
> sync to the network files on the server.
>
> I have it set up to keep a local copy of a mapped network drive that holds my
> files (Cygwin $HOME). As I understand it (eg. explained in
> https://docs.microsoft.com/en-us/windows-server/storage/folder-redirection/folder-redirection-rup-overview),
> when the system goes offline, Windows uses the "Folder Redirection" feature to
> redirect access to the client-side cache, C:\Windows\CSC.
>
> I guess Cygwin can choke on this redirected path.
>> It would also help if you could capture the assertion failure in a debugger. Do
>> you know how to use gdb? If so, I would suggest attaching gdb to bash before
>> hibernating, and putting a breakpoint at symlink_info::check. Assuming that gdb
>> is still usable after you resume from hibernation, we ought to be able to find
>> the cause of the assertion failure.
>
> I will try this, but it will be tricky, because I don't get the assertion every
> time I go offline / hibernate. I'll see if I can work out how to provoke the bug
> reliably. I don't remember the situation from every time it's happened, but I
> think perhaps it can happen if there is a bash window open at the time. bash
> still works, but it can't run anything else, nor can I start any new processes.
> If so, your test might be possible, but might not see the symptom, since the
> problem seems to be in processes started by bash. But I'll try.
Hi Tim,
I don't know if you noticed the thread starting here:
https://cygwin.com/ml/cygwin/2019-12/msg00016.html
The problem reported there has been fixed, and I hope that the fix also works
for your problem. You can test it by installing the latest snapshot from
https://cygwin.com/snapshots/.
Thanks.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple