From: Ken Brown <kbrown@cornell.edu>
To: David Dyck <david.dyck@gmail.com>, cygwin@cygwin.com
Subject: Re: ag 2 <(echo 2) gets assertion "p >= path" failed: .. /cygwin-3.1.7 ... /cygwin/path.cc", line 3065, function: int symlink_info::check
Date: Sun, 6 Sep 2020 15:47:14 -0400 [thread overview]
Message-ID: <26aedc53-30f2-d1a2-f9e8-c8a5dfa548c1@cornell.edu> (raw)
In-Reply-To: <CAJtSMgtgAvB3Fin-gtmU5qr3xYnq4_53S2UD3yqAVDVMkAfMSQ@mail.gmail.com>
On 9/6/2020 2:43 PM, David Dyck via Cygwin wrote:
> This command triggers an assertion failure
> "ag" is from the_silver_searcher
>
> $ ag 2 <(echo 2)
> assertion "p >= path" failed: file
> "/home/corinna/src/cygwin/cygwin-3.1.7/cygwin-3.1.7-1.x86_64/src/newlib-cygwin/winsup/cygwin/path.cc",
> line 3065, function: int symlink_info::check(char*, const
> suffix_info*, fs_info&, path_conv_handle&)
> Aborted (core dumped)
>
> 3473k 2020/08/22 C:\cygwin64\bin\cygwin1.dll
> Cygwin DLL version info:
> DLL version: 3.1.7
> bash 4.4.12-3 OK
> the_silver_searcher 2.2.0-1 OK
[...]
> assertion "p >= path" failed: file
> "/home/corinna/src/cygwin/cygwin-3.1.7/cygwin-3.1.7-1.x86_64/src/newlib-cygwin/winsup/cygwin/path.cc",
> line 3065, function: int symlink_info::check(char*, const
> suffix_info*, fs_info&, path_conv_handle&)
> Aborted (core dumped)
[...]
> I've reported this on github as an "ag" bug, but I think it is a bug in cygwin
An assertion failure in Cygwin code is a Cygwin bug. I'll take a look.
Ken
next prev parent reply other threads:[~2020-09-06 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 18:43 David Dyck
2020-09-06 19:07 ` Eliot Moss
2020-09-06 22:15 ` David Dyck
2020-09-06 23:19 ` Eliot Moss
2020-09-06 19:47 ` Ken Brown [this message]
2020-09-06 20:28 ` Ken Brown
2020-09-07 20:35 ` Ken Brown
2020-09-08 19:26 ` Ken Brown
2020-09-08 19:32 ` Ken Brown
2020-09-09 3:48 ` David Dyck
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=26aedc53-30f2-d1a2-f9e8-c8a5dfa548c1@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=david.dyck@gmail.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).