[bug-diffutils] bug#64811: bug#64811: Win-version now broken

2024-03-01 Thread Paul Eggert
On 2024-03-01 09:29, Gisle Vanem wrote: Some added trace shows:    diff.c(844): &noparent: 0x7FF6A9438478    diff.c(1548): file[0].name: 'h:\Cygwin64', st_mode: S_ISDIR, size: -1, toplevel: 1    diff.c(1548): file[1].name: 'f:\Cygwin64', st_mode: S_ISDIR, size: -1, toplevel: 1 My guess is

[bug-diffutils] bug#64811: bug#64811: Win-version now broken

2024-02-27 Thread Paul Eggert
On 2024-02-27 03:02, Gisle Vanem via bug-diffutils via All diffutils discussion. wrote: Some added trace shows:   diff.c(844): &noparent: 0x7FF6A9438478   diff.c(1548): file[0].name: 'h:\Cygwin64', st_mode: S_ISDIR, size: -1, toplevel: 1   diff.c(1548): file[1].name: 'f:\Cygwin64', st_mod

[bug-diffutils] bug#64811: bug#64811: Win-version now broken

2023-08-01 Thread All diffutils discussion.
Paul Eggert wrote: in my test:    diff --recursive does not work. What are the failure symptoms? Is this something you can debug? I don't use MS-Windows and won't be of much help on that platform. My guess would be in the fdopendir area; perhaps that guess will help you debug. Correct.

[bug-diffutils] bug#64811: bug#64811: Win-version now broken

2023-07-24 Thread Paul Eggert
On 2023-07-24 04:18, Gisle Vanem wrote: Off-course, otherwise diff.exe wouldn't have linked. Would it? I don't know, but I added them by installing the attached patch. in my test:   diff --recursive does not work. What are the failure symptoms? Is this something you can debug? I don'