From owner-freebsd-current Mon Dec 7 09:29:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21749 for freebsd-current-outgoing; Mon, 7 Dec 1998 09:29:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21744 for ; Mon, 7 Dec 1998 09:29:04 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA10589; Mon, 7 Dec 1998 10:28:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA02857; Mon, 7 Dec 1998 10:28:41 -0700 Date: Mon, 7 Dec 1998 10:28:41 -0700 Message-Id: <199812071728.KAA02857@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Robert Nordier Cc: syssgm@dtir.qld.gov.au (Stephen McKay), freebsd-current@FreeBSD.ORG Subject: Re: strings - elf vs aout In-Reply-To: <199812071450.QAA26709@ceia.nordier.com> References: <199812071001.UAA09667@nymph.dtir.qld.gov.au> <199812071450.QAA26709@ceia.nordier.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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'. Then 'strings' for ELF is broken, since \t is not a newline of end of a string, and Steven's comments are valid. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message