hello,

I can confirm the bug and add the detail that it also segfault if the empty pattern is in a file:

quark:~# cat /dev/null > /tmp/patt ; fgrep -i -f /tmp/patt
Segmentation fault

shouldn't the severity be higher than 'normal' for a problem like this which is logged in the kernel ring buffer and so is shown in the output of dmesg every time a (bad) script invoke this bug?

quark:~# dmesg | tail -n 2
[59128.902200] fgrep[6320]: segfault at 0 ip 000000000040887d sp 00007fffc282d650 error 6 in fgrep[400000+12000] [59141.910302] fgrep[6321]: segfault at 0 ip 000000000040887d sp 00007fff4697ee10 error 6 in fgrep[400000+12000] [59154.288166] fgrep[6869]: segfault at 0 ip 000000000040887d sp 00007fffbd19f3d0 error 6 in fgrep[400000+12000] [59172.273363] fgrep[6872]: segfault at 0 ip 000000000040887d sp 00007fffa1ca7fa0 error 6 in fgrep[400000+12000] [59185.136186] fgrep[6882]: segfault at 0 ip 000000000040887d sp 00007fff72fc9170 error 6 in fgrep[400000+12000] [59214.643752] fgrep[8283]: segfault at 0 ip 000000000040887d sp 00007fff4809a880 error 6 in fgrep[400000+12000] [59516.308163] fgrep[10673]: segfault at 0 ip 000000000040887d sp 00007ffff26708e0 error 6 in fgrep[400000+12000] [59521.371854] fgrep[10675]: segfault at 0 ip 000000000040887d sp 00007fff95bf0a90 error 6 in fgrep[400000+12000] [59536.459643] fgrep[10768]: segfault at 0 ip 000000000040887d sp 00007fffccd728e0 error 6 in fgrep[400000+12000] [59551.290645] fgrep[10848]: segfault at 0 ip 000000000040887d sp 00007fff788a08c0 error 6 in fgrep[400000+12000]

(I added this to have it indexed by search engines so it may help other to understand why they have this strange logs in dmesg)

--
bye,
emilio



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to