Date: Sat, 6 Apr 2013 11:21:41 -0900 (AKST) From: Joe Public <root@ai1.alaska.net> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/177673: Possible comment problem is /bin/sh Message-ID: <201304062021.r36KLfWL085499@ai1.alaska.net> Resent-Message-ID: <201304062030.r36KU0P1073735@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 177673 >Category: bin >Synopsis: Possible comment problem is /bin/sh >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 06 20:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Joe Public >Release: FreeBSD 9.1-RELEASE i386 >Organization: none >Environment: System: FreeBSD 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: /bin/sh comments in a script will attach to an adjacent string. An simple example follows, but they also attach in assignments, etc. This broke 4.11 scripts, so I know sh(1) has changed since then, but I am not qualified to state whether the current or previous behavior is correct. >How-To-Repeat: #!/bin/sh echo 'a comment follows'#comment. $ ./script $ a comment follows#comment. >Fix: Requires someone knowledgeable with /bin/sh code. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304062021.r36KLfWL085499>