GNU bug report logs -
#71079
Bug Report: Unexpected Termination of grep Process
Previous Next
Full log
View this message in rfc822 format
[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)]
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.