abrt 1.0.8 detected a crash. architecture: x86_64 cmdline: column -t -s# comment: If necessary I can upload most, though not all, of the files that triggered the issue. component: util-linux-ng executable: /usr/bin/column kernel: 2.6.32.10-90.fc12.x86_64 package: util-linux-ng-2.16.2-7.fc12 rating: 4 reason: Process /usr/bin/column was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce: 1. paste '-d#' f1 f2 | column -t '-s#' backtrace ----- warning: section .dynbss not found in /var/cache/abrt-di/usr/lib/debug/.build-id/eb/2a5f2c584b770ea80188bcb86dbeb9ce221b3c.debug warning: section .dynbss not found in /var/cache/abrt-di/usr/lib/debug/.build-id/eb/2a5f2c584b770ea80188bcb86dbeb9ce221b3c.debug warning: section .dynbss not found in /var/cache/abrt-di/usr/lib/debug/.build-id/eb/2a5f2c584b770ea80188bcb86dbeb9ce221b3c.debug Core was generated by `column -t -s#'. Program terminated with signal 11, Segmentation fault. #0 __wcslen (s=0x0) at wcslen.c:30 30 wcslen.c: No such file or directory. in wcslen.c Thread 1 (Thread 14562): #0 __wcslen (s=0x0) at wcslen.c:30 len = 0 #1 0x00000032f6068c3e in fputws (str=0x0, fp=0x32f6373780) at iofputws.c:37 len = 75 result = <value optimized out> #2 0x0000000000401715 in maketbl (argc=<value optimized out>, argv=<value optimized out>) at column.c:274 t = <value optimized out> p = <value optimized out> cols = <value optimized out> lp = 0x1613498 lens = <value optimized out> maxcols = <value optimized out> wcstok_state = 0x0 coloff = <value optimized out> cnt = <value optimized out> i = <value optimized out> #3 main (argc=<value optimized out>, argv=<value optimized out>) at column.c:140 win = {ws_row = 62, ws_col = 237, ws_xpixel = 0, ws_ypixel = 0} fp = <value optimized out> ch = <value optimized out> tflag = <value optimized out> xflag = <value optimized out> p = <value optimized out> From To Syms Read Shared Object Library 0x00000032f601e860 0x00000032f61261bc Yes (*) /lib64/libc.so.6 0x00000032f5c00af0 0x00000032f5c183d4 Yes (*) /lib64/ld-linux-x86-64.so.2 (*): Shared library is missing debugging information. $1 = 0x0 No symbol "__glib_assert_msg" in current context.
Created attachment 404830 [details] File: backtrace
Garrett, thanks for your bug report. Do you still have the files that triggered the problem? I cannot reproduce this issue.
The smallest test case I was able to reproduce this problem with was with f1 being an empty file and f2 being a one-byte file containing just a single line feed. I can attach them if you want, though I suspect that won't be necessary. ;-)
A slightly-smaller test case that doesn't involve any files: echo % | column -t -s%
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This still happens in util-linux-ng-2.18-4.4.fc14. Does upstream have a bugtracker I could go to?
(In reply to comment #6) > This still happens in util-linux-ng-2.18-4.4.fc14. Does upstream have a > bugtracker I could go to? I'm able to reproduce the problem by "echo % | column -t -s%". Thanks, I'm fix it asap. (...and sorry for delay).
Fixed by upstream commit 3f7fc4d43b61e442b81937aa06e079950a8ebb7c ...will be fixed in Fedora later.
That fix works for me. Thanks! Shall I clone this against el6 as well?
(In reply to comment #9) > That fix works for me. Thanks! Shall I clone this against el6 as well? Thanks for verification. I have created the clone.
FWIW, this is fixed in util-linux-2.19.1-1.4.fc15.x86_64, but not yet in util-linux-ng-2.18-4.8.fc14.x86_64.
Closing since F14 is now EOL...