Your message dated Fri, 25 Apr 2014 17:47:28 +0200
with message-id <[email protected]>
and subject line Re: Bug#696717: gawk: linefeed(?) from stdin does replace
chars on print
has caused the Debian Bug report #696717,
regarding gawk: linefeed(?) from stdin does replace chars on print
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
696717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696717
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gawk
Version: 1:3.1.7.dfsg-5
Severity: normal
While for example you get stdin from ssh piped and there's linefeed after
value, the gawk makes replace chars from the start of line printed out with
print. For example if you print from input "100" with '{ print "value.from "
$1 "000" }' that does not print correct value.from 100000 but 000ue.from 100
So for example this:
ssh -q -o "StrictHostKeyChecking no" [email protected] ipv6 fire conn print
count | awk '{ print "IPv6.value " $1 "000" }'
prints out wrong line "0006.value 535"
but
ssh -q -o "StrictHostKeyChecking no" [email protected] ipv6 fire conn print
count |sed 's/.$//g'| awk '{ print "IPv6.value " $1 "000" }'
gives correct "IPv6.value 585000"
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gawk depends on:
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
gawk recommends no packages.
gawk suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I am closing this bug because of the lack of information and the fact that the
reporter cannot be reached.
What I think is happening here is that the input contains bare carriage returns
('\r'). The following example demonstrates what could have happend:
$ printf "foo\rbar" | gawk "{ print }"
bar
Did gawk eat foo? No, it was the terminal:
$ printf "foo\rbar | gawk "{ print }" | cat -v
foo^Mbar
If this is the case, the solution is to fix the output of the offending
program.
Regards,
Jeroen Schot
--- End Message ---
