Date: Mon, 7 Dec 1998 16:50:32 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: syssgm@dtir.qld.gov.au (Stephen McKay) Cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: strings - elf vs aout Message-ID: <199812071450.QAA26709@ceia.nordier.com> In-Reply-To: <199812071001.UAA09667@nymph.dtir.qld.gov.au> from Stephen McKay at "Dec 7, 98 08:01:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen McKay wrote: > There's an annoying anomaly in the new version of strings. The traditional > version specifically included tabs as valid characters for strings, while > the new one doesn't, leading to: > > $ printf 'My dog has\tno nose' > foo > $ strings -aout foo > My dog has no nose > $ strings -elf foo > My dog has > no nose > $ > > I run "strings" on lots of files (eg frobnoz.doc), not just executables. > This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE > kernel compile option which now requires "strings -aout" to recover the > config file. > > Shall I devise and commit a fix for this behaviour? If you want to do this, I'd suggest making it an option. Current standards, such as the Single UNIX Specification, apparently regard a printable string as 4 or more isprint(3) chars followed by '\n' or '\0'. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812071450.QAA26709>