grep is terminated by signal 11 while scanning /home/ directory in find: the command was find /home/ /u1/ -type f -exec grep -H 'Michigan' {} ';' find: grep terminated by signal 11 This failure is hard to reproduce, when I started the `find' second time there was no such error. Also it is hard to guess on what file the error was, because grep prints only on matched files. I can just guess the files were from FC6 distribution. -rw-r--r-- 1 root root 708780032 Oct 29 19:23 /home/data/FC-6-i386-disc1.iso -rw-r--r-- 1 root root 3525195776 Oct 24 22:32 /home/data/FC-6-i386-DVD.iso rpm -q grep grep-2.5.1-54.1.2.fc6
Created attachment 159541 [details] Transcript of grep invocations Patch #15 (grep-mem-exhausted.patch) appears to be the culprit. grep is dumping core on line 790 of src/grep.c: 790 oldc = beg[-1];
I'm trying to come up with way to reproduce input which triggers the problem without sending you a tarball of my entire test directory. The test case I ran processes about 36M (in 120 files) of a directory tree before choking on a 473M sparse file (only 228K on disk). I'll send directions if I can reproduce something, but for now: Patch15 removes an error in some cases, but causes a segmentation violation in others.
(In reply to comment #2) > [...] for now: Patch15 removes an error in some cases, but causes a segmentation violation in others. OK, thanks. For start, I'll study the patch and try to find the cause by a mental debugging. ;-)
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug still exists in Fedora 8.
thank you for your update
egrep, fgrep, grep are still broken in Fedora 9 and Red Hat Enterprise Linux Server release 5.2 (Tikanga). It is easy to get segfaults and infinite loops: [pacman@labyrinth bug]$ dd if=/dev/zero of=zero300 bs=1024k count=300 300+0 records in 300+0 records out 314572800 bytes (315 MB) copied, 4.99563 s, 63.0 MB/s [pacman@labyrinth bug]$ /bin/grep a zero300 Segmentation fault (core dumped) [pacman@labyrinth bug]$ dd if=/dev/zero of=zero280 bs=1024k count=280 280+0 records in 280+0 records out 293601280 bytes (294 MB) copied, 4.42342 s, 66.4 MB/s [pacman@labyrinth bug]$ /bin/grep a zero280 ^C <---- seems like grep will loop forever so I interrupted it If you remove: grep-mem-exhausted.patch then the problem goes away.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.