3.0.7(0.338/5/3): Possible reference to Developer's instances of dev files in deployed build

[Ken Brown]

On 12/4/2019 5:40 AM, Wilfed Olaf Sulla via cygwin wrote:
> Hi,
> 
> Cygwin is core dumping with the following message:
> 
> 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&)
> 
> 
> To recreate this event:
> 
> shackleton:sulla:$ cd /cygdrive/
> shackleton:sulla:$ ls -la
> 
> 
> Build:
> 
> CYGWIN_NT-6.1 shackleton 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin
> Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1
> 
> -	Yes, it is an old machine that has been around for a while, but it
> 	does the job asked of it.
> 
> 
> A similar event seems to have cropped up before, with a pair of patches
> following:
> 
> 	Re: winsup\cygwin\path.cc issues
> 	https://sourceware.org/ml/cygwin/2018-05/msg00315.html
> 
> 	Cygwin: normalize_win32_path: Avoid buffer underruns
> 	https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=35998fc2fa6c

There was also a more recent example:

     https://cygwin.com/ml/cygwin/2019-09/msg00228.html ,

which was fixed here:

     https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=283cb372e

Please try the test release cygwin-3.1.0-0.8 to see if the fix also works for 
your case.  If not, can you figure out which file in /cygdrive causes 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