From: Tim Adye <T.J.Adye@rl.ac.uk>
To: <cygwin@cygwin.com>
Subject: Re: assertion "p >= path" failed
Date: Wed, 30 Oct 2019 23:56:00 -0000 [thread overview]
Message-ID: <46bc0b2e-a138-3e25-a403-4f3d6eff1651@rl.ac.uk> (raw)
In-Reply-To: <5b60cc71-fa1b-b972-10be-b37ff5756fab@rl.ac.uk>
Hi Ken,
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&)
Again following resume from hibernation after going offline with the
offline files as HOME (H:\). Again the only way out of the issue is to
reboot.
Any other ideas to help me diagnose?
Thanks,
Tim.
On 26/10/2019 22:15, Tim Adye wrote:
> Hi Ken,
>
> Thanks for the promising idea. I could reproduce the assertion with
> the examples like '\\?\DRIVE' given in the other thread, so I have now
> upgraded to cygwin-3.1.0-0.7. This fixes the '\\?\DRIVE' assertion.
> Since my case only happens from time to time, I'll have to wait and
> see if it happens again. I'll let you know if it does.
>
> Thanks,
> Tim.
>
> On 26/10/2019 02:00, Ken Brown wrote:
>> On 10/25/2019 6:07 PM, Tim Adye wrote:
>>> Hi again,
>>>
>>> Thanks for all the interesting detective work investigating my
>>> problem with
>>> ssh-agent. Let's hope it results in a fix.
>>>
>>> I have another problem which is a bit harder to reproduce, but
>>> perhaps has a
>>> clearer signature. From time to time my PC gets into a state where
>>> no Cygwin
>>> command will start. They all exit with the message:
>>>
>>> C:\>C:\cygwin\bin\bash.exe
>>> assertion "p >= path" failed: file
>>> "/home/corinna/src/cygwin/cygwin-3.0.7/cygwin-3.0.7-1.x86_64/src/newlib-cygwin/winsup/cygwin/path.cc",
>>>
>>> line 2916, function: int symlink_info::check(char*, const suffix_info*,
>>> fs_info&, path_conv_handle&)
>> This might be the same bug that was reported here:
>>
>> https://cygwin.com/ml/cygwin/2019-09/msg00228.html .
>>
>> That bug has been fixed. Please try the test release
>> cygwin-3.1.0-0.7 and see
>> if you still have the problem.
>>
>> 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
>>
>
>
> --
> 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
>
--
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
next prev parent reply other threads:[~2019-10-30 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 22:07 Tim Adye
2019-10-26 1:00 ` Ken Brown
2019-10-26 21:16 ` Tim Adye
2019-10-30 23:56 ` Tim Adye [this message]
2019-10-31 18:19 ` Ken Brown
2019-11-04 12:51 ` Tim Adye
2019-12-11 23:51 ` Ken Brown
2019-12-16 8:35 ` Tim Adye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46bc0b2e-a138-3e25-a403-4f3d6eff1651@rl.ac.uk \
--to=t.j.adye@rl.ac.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).