public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: assertion "p >= path" failed
Date: Thu, 31 Oct 2019 18:19:00 -0000	[thread overview]
Message-ID: <f86de3f3-3a40-f189-8944-545b3c3aab57@cornell.edu> (raw)
In-Reply-To: <46bc0b2e-a138-3e25-a403-4f3d6eff1651@rl.ac.uk>

[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.

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.

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

  reply	other threads:[~2019-10-31 18:19 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
2019-10-31 18:19       ` Ken Brown [this message]
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=f86de3f3-3a40-f189-8944-545b3c3aab57@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).