Re: 5.3-RELEASE and cut(1) bug
From: jpd (read_the_sig_at_do.not.spam.it.invalid)
Date: 11/13/04
- Next message: Dave Aas: "Re: XBOX Live"
- Previous message: vladimir_at_math.uic.edu: "Re: 5.3-RELEASE and cut(1) bug"
- In reply to: james
hal-pc.org: "5.3-RELEASE and cut(1) bug" - Next in thread: james
hal-pc.org: "Re: 5.3-RELEASE and cut(1) bug" - Reply: james
hal-pc.org: "Re: 5.3-RELEASE and cut(1) bug" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 13 Nov 2004 01:00:51 GMT
Begin <41955385$0$10438$a726171b@news.hal-pc.org>
On 2004-11-13, "james <at> hal-pc.org" <> wrote:
> wasn't sure if any of you have come across this or if i'm just loosing my
> mind
> (good posability of the latter).
You're writing like you need sleep. 8-)
[snip: mixer(8) output causes cut(1) to fail on fbsd 5.3]
> what's even more strange is that if you reproduce the same (visible) output
> of
> "mixer -s vol" and send it to the "broken" cut with echo or from within a
> file
> it works:
> $ echo "vol 34:34" | /usr/bin/cut -d : -f 2
> 34
I can reproduce your error on 5.3B7, where 4.9R seems to work fine.
Additionally, the output of mixer -s vol | hexdump -C looks identical on
both (down to the actual numbers, I wonder why that is).
I just had cvsweb get me a diff on cut(1) source between 5.2.1 and 5.3,
and the difference seems to be mainly multibyte support. I couldn't find
the exact error message in the file so I assume it is somewhere in a
library. ICBW; It didn't show up in a grep of the libc source either.
Time for a PR, I think.
-- j p d (at) d s b (dot) t u d e l f t (dot) n l .
- Next message: Dave Aas: "Re: XBOX Live"
- Previous message: vladimir_at_math.uic.edu: "Re: 5.3-RELEASE and cut(1) bug"
- In reply to: james
hal-pc.org: "5.3-RELEASE and cut(1) bug" - Next in thread: james
hal-pc.org: "Re: 5.3-RELEASE and cut(1) bug" - Reply: james
hal-pc.org: "Re: 5.3-RELEASE and cut(1) bug" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|