Skip to main content

Timeline for Best way to grep a big binary file?

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
Oct 17, 2023 at 3:38 history edited phuclv CC BY-SA 4.0
added 2 characters in body
Oct 16, 2023 at 5:06 comment added phuclv @ott-- The OP is using Linux so there's no --mmap at all. It's an option in BSD grep
Oct 10, 2023 at 7:13 history edited Ciro Santilli OurBigBook.com CC BY-SA 4.0
grammar
Oct 9, 2023 at 23:44 answer added Ciro Santilli OurBigBook.com timeline score: 2
Oct 12, 2021 at 13:19 comment added Totor Maybe this could work grep --only-matching --byte-offset --binary. The --only-matching option can be implemented without buffering the whole line, but I don't know if your implementation does take advantage of this to actually save memory. --byte-offset will indicate where the matching sequence starts in the binary data stream or blob.
Oct 12, 2021 at 11:11 answer added IPv6 timeline score: 0
Aug 13, 2015 at 22:44 answer added Michael Martinez timeline score: 1
Aug 13, 2015 at 22:13 comment added Parthian Shot @ott-- Real programmers would do it in Fortran.
Aug 13, 2015 at 21:49 comment added Michael Martinez @ott your vim answer piqued my interest. Does vim really only load what it needs into memory? A quick internet search is not conclusive. Some people say it still has a hard time with large files. Others say "Ctrl-c" will stop it trying to load everything into RAM. So I'm not sure whether your answer is correct.
Aug 13, 2015 at 20:52 comment added ott-- Have you tried grep --mmap ... already? Real programmers would do that with vim -R -b 400gbfile and then /pattern.
Aug 13, 2015 at 20:50 answer added jlliagre timeline score: 7
Aug 13, 2015 at 20:42 review First posts
Aug 13, 2015 at 20:54
Aug 13, 2015 at 20:41 history asked Just User CC BY-SA 3.0