GNU bug report logs -
#71079
Bug Report: Unexpected Termination of grep Process
Previous Next
To reply to this bug, email your comments to 71079 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-grep <at> gnu.org
:
bug#71079
; Package
grep
.
(Mon, 20 May 2024 14:07:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Joseph Joshua <okikijoshua123 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-grep <at> gnu.org
.
(Mon, 20 May 2024 14:07:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Dear GNU Grep Maintainers,
I have upgraded to GNU grep version 3.11 and re-ran the test.
Unfortunately, the issue persists. Below are the detailed steps and the
transcript of the commands and their outputs:
### System Information:
- **Grep Version**: 3.11
- **Operating System**: Debian GNU/Linux 12 (bookworm)
- **Memory**:
- Total RAM: 2.7 GiB
- Used RAM: 1.8 GiB
- Free RAM: 594 MiB
- Shared: 64 MiB
- Buff/Cache: 331 MiB
- Available: 926 MiB
- Swap: Not configured
### Steps to Reproduce:
1. **Directory Listing**:
```bash
$ ls -l /path/to/directory
total 4
-rw-r--r-- 1 user user 20 May 17 12:34 file1.txt
-rw-r--r-- 1 user user 15 May 17 12:34 file2.txt
drwxr-xr-x 2 user user 4096 May 17 12:34 subdir
```
2. **Command Execution with Specific Pattern**:
```bash
$ grep -r 'specific_pattern' /path/to/directory
```
3. **Output and Errors**:
```plaintext
$ script -c "grep -r 'specific_pattern' /path/to/directory" output.log
Script started, file is output.log
The build failed because the process exited too early. This probably
means the system ran out of memory or someone called `kill -9` on the
process.
Usage: grep [OPTION]... PATTERNS [FILE]...
Try 'grep --help' for more information.
Script done, file is output.log
```
Please let me know if further information is required to diagnose and
resolve this issue.
Thank you for your assistance.
Yours faithfully,
Joshua
09023556682
okikijoshua123 <at> gmail.com
[Message part 2 (text/html, inline)]
Merged 71013 71079.
Request was from
Paul Eggert <eggert <at> cs.ucla.edu>
to
control <at> debbugs.gnu.org
.
(Mon, 20 May 2024 15:00:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#71079
; Package
grep
.
(Mon, 20 May 2024 15:05:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 71079 <at> debbugs.gnu.org (full text, mbox):
On 2024-05-17 05:52, Joseph Joshua wrote:
> 1. Run the following command as part of a build process: grep -r 'pattern'
> /path/to/directory
Please give us a way to reproduce the bug; including the actual pattern
that you're using. Otherwise we won't be able to help.
Also, please reply to <71079 <at> debbugs.gnu.org> instead of creating a new
bug report for each email message.
Thanks.
Information forwarded
to
bug-grep <at> gnu.org
:
bug#71079
; Package
grep
.
(Mon, 20 May 2024 18:06:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 71079 <at> debbugs.gnu.org (full text, mbox):
Joseph Joshua <okikijoshua123 <at> gmail.com> writes:
$ ls -l /path/to/directory
total 4
-rw-r--r-- 1 user user 20 May 17 12:34 file1.txt
-rw-r--r-- 1 user user 15 May 17 12:34 file2.txt
drwxr-xr-x 2 user user 4096 May 17 12:34 subdir
Does this mean that the actual name of the directory is
/path/to/directory, or is that a placeholder for the real name?
Although that isn't likely to matter much.
And since you're running "grep -r" and grep is looking into files in
subdirectories, for completeness, what is "ls -alR"?
> 3. **Output and Errors**:
> ```plaintext
> $ script -c "grep -r 'specific_pattern' /path/to/directory" output.log
> Script started, file is output.log
> The build failed because the process exited too early. This probably
> means the system ran out of memory or someone called `kill -9` on the
> process.
> Usage: grep [OPTION]... PATTERNS [FILE]...
> Try 'grep --help' for more information.
> Script done, file is output.log
> ```
Can you please check whether lines containing "The build failed because
the process exited too early" or "Usage: grep" occur in any of the files
in /path/to/directory?
But as others have noted, telling us what "specific_pattern" is is
essential if we're to give you any help.
Dale
This bug report was last modified 1 year and 27 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.