[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44713: grep -F not working
From: |
Keith Robertson |
Subject: |
bug#44713: grep -F not working |
Date: |
Thu, 19 Nov 2020 16:06:16 +0000 |
Thanks for apprising me of the proper forum for this!
I found an issue there which addresses this and provided a workaround.
https://github.com/git-for-windows/git/issues/2434
Kind regards,
Keith
-----Original Message-----
From: Dimitry Andric <dimitry@andric.com>
Sent: Thursday, November 19, 2020 4:40 AM
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Keith Robertson <krobertson@vmware.com>; 44713-done@debbugs.gnu.org
Subject: Re: bug#44713: grep -F not working
On 17 Nov 2020, at 23:14, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 11/17/20 12:53 PM, Keith Robertson wrote:
>
>> 0 [main] grep 747 cygwin_exception::open_stackdumpfile: Dumping
>> stack trace to grep.exe.stackdump
>
> Looks like a configuration problem of some sort. I think you'll need to
> contact whoever packaged Git for Windows for you, as the grep developers
> generally don't do Microsoft Windows.
This is the grep executable that is shipped as part of the Git distribution for
Windows [1] [2].
Indeed I can reproduce the error exactly as shown, in a Windows environment
with the latest Git 2.29.2 installed:
D:\>echo abc | "C:\Program Files\Git\usr\bin\grep.exe" -iqF d
0 [main] grep 855 cygwin_exception::open_stackdumpfile: Dumping stack
trace to grep.exe.stackdump
D:\>type grep.exe.stackdump
Stack trace:
Frame Function Args
000FFFFBDC8 001800644A0 (000FFFFBFE8, 00000000002, 00000000000, 000FFFFDE50)
000FFFFDE50 001800666CC (00000000064, 00000000000, 000000001EC, 00000000000)
000FFFFC4F0 0018014AEE8 (00100000000, 00000000000, 00000000000, 00000000000)
00100435E60 001801750E4 (00000000000, 00000000000, 001800D6DBE, 000FFFFC740)
00100435E60 001801471EB (00180045BCF, 00000000000, 000000000B5, 000000000B5)
00100435E60 00180219CB8 (00800041850, 00800041720, 001801701B8, 000FFFFC830)
00100435E60 00100407648 (00800041758, 00000000000, 00800041850, 00000000000)
000FFFFCB40 0010040483C (00000000001, 00000000001, 00000000000, 00000000000)
000FFFFCB40 00100428CCB (00000000020, 8080808080808080, 0018004AE9E,
000FFFFCC70)
000FFFFCCE0 0018004AF0A (00000000000, 00000000000, 00000000000, 00000000000)
000FFFFFFF0 00180048846 (00000000000, 00000000000, 00000000000, 00000000000)
000FFFFFFF0 001800488F4 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace
Unfortunately the stack trace isn't really helpful. :-)
Keith, I suggest you report this on the GitHub issue tracker of git-for-windows
[3].
-Dimitry
[1] https://git-scm.com/download/win
[2] https://github.com/git-for-windows/git
[3] https://github.com/git-for-windows/git/issues