Package: coreutils
Version: 5.97-5.3
Severity: normal

    While running cut over some screen logs (which include escape
    characters), I managed to cause cut to segfault with the message:

*** glibc detected *** double free or corruption (top): 0x0000000000507320 ***

    The backtrace isn't particularly helpful either:

Core was generated by `cut -f2 -d( file0 file1'.
Program terminated with signal 6, Aborted.
#0  0x00002b89bcbc707b in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00002b89bcbc707b in raise () from /lib/libc.so.6
#1  0x00002b89bcbc884e in abort () from /lib/libc.so.6
#2  0x00002b89bcbfd629 in ?? () from /lib/libc.so.6
#3  0x00002b89bcc04193 in ?? () from /lib/libc.so.6
#4  0x00002b89bcc0421e in free () from /lib/libc.so.6
#5  0x00000000004017b1 in ?? ()
#6  0x0000000000401f11 in ?? ()
#7  0x00002b89bcbb44ca in __libc_start_main () from /lib/libc.so.6
#8  0x000000000040112a in ?? ()
#9  0x00007fffee026958 in ?? ()
#10 0x0000000000000000 in ?? ()

    I've attached a test case that consistently elicits the behavior
    from cut on my unstable amd64 machines.  Simply run the 'test.sh'
    script.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20-amd64-rse
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages coreutils depends on:
ii  libacl1                     2.2.42-1     Access control list shared library
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libselinux1                 1.32-3       SELinux shared libraries

coreutils recommends no packages.

-- no debconf information

-- 
Robert Edmonds
[EMAIL PROTECTED]

Attachment: cut_core_dump.tar.gz
Description: Binary data

Attachment: signature.asc
Description: Digital signature

Reply via email to