Description of Problem: When nkf is applied to a filename it only "outputs" a sequence of "\o"s (16KiB of them). Version-Release number of selected component (if applicable): (nkf-1.92-8) How Reproducible: Every time. Steps to Reproduce: 1. nkf some/file Actual Results: No output appears on a terminal. Expected Results: The filtered output should appear on the terminal. Additional Information: "nkf < some/file" works correctly without any problem. I think this problem is likely caused by the change of malloc in glibc-2.3. I spotted this problem because semi.spec uses nkf to convert the encoding of its Japanese info file, and this problem breaks that.
Created attachment 59344 [details] strace output
Created attachment 59345 [details] patch to let glibc allocate the input file buffer
With this patch it seems to work fine, though I don't really see why it doesn't work with the buffer nkf allocates for input.
See http://sources.redhat.com/ml/libc-hacker/2002-06/msg00005.html
a workaround like the above was added to nkf in 1.92-9
This should be fixed in glibc-2.2.90-14.
Thanks. I checked it is working, by rebuilding nkf without the above patch, and indeed it appears to work just fine. So I guess the patch could be dropped the next time the nkf package is updated.