Your message dated Fri, 01 Nov 2013 10:35:15 -0400 with message-id <[email protected]> and subject line [wall] hangs on multi-line input (100%CPU) has caused the Debian Bug report #307438, regarding [wall] hangs on multi-line input (100%CPU) 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.) -- 307438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=307438 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bsdutils Version: 1:2.12-10 Severity: normal File: /usr/bin/wall /usr/bin/wall Setting up bsdutils (2.12-10) / testing ad873b3707cea67dcce24074ec2de31c multi-line input for "wall" hangs (100%CPU): ex: echo -e "wagga\nwagga\n"|wall It works correctly with the unstable bsdutils (2.12p-4) 6d99e8f733a6e4303ece4cdfa6b99dd6. I guess it's a simple one and the following is of no real use - wall performs no syscalls while eating up 100% CPU. [0]--(05:40:45)-(root@km)-(~)-> gdb $(which wall) 28653 GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". Attaching to program: /usr/bin/wall, process 28653 Failed to read a valid object file image from memory. Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/tls/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libnss_compat.so.2 Reading symbols from /lib/tls/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libnsl.so.1 Reading symbols from /lib/tls/libnss_nis.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/tls/libnss_nis.so.2 Reading symbols from /lib/tls/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libnss_files.so.2 0xb7f100cb in mallopt () from /lib/tls/libc.so.6 (gdb) (gdb) bt #0 0xb7f100cb in mallopt () from /lib/tls/libc.so.6 #1 0xb7f0f8fb in mallopt () from /lib/tls/libc.so.6 #2 0xb7f0ec43 in malloc () from /lib/tls/libc.so.6 #3 0x08049447 in ?? () #4 0x0000028e in ?? () #5 0x00000003 in ?? () #6 0xbffff850 in ?? () #7 0x0804b8f0 in ?? () #8 0xb7fcee80 in ?? () from /lib/tls/libc.so.6 #9 0x00000022 in ?? () #10 0x08049bfc in _IO_stdin_used () #11 0x0804e000 in ?? () #12 0x0804cff8 in ?? () #13 0x00000003 in ?? () #14 0xb7fd19e0 in _obstack () from /lib/tls/libc.so.6 #15 0x4276f27b in ?? () #16 0x706d742f in ?? () #17 0x61772f2f in ?? () #18 0x792e6c6c in ?? () #19 0x6b306870 in ?? () #20 0x00000073 in ?? () #21 0xbffff6c0 in ?? () #22 0xbffff6c0 in ?? () ---Type <return> to continue, or q <return> to quit--- #23 0xbffff4d8 in ?? () #24 0x6c6c000a in ?? () #25 0xb7000a6f in ?? () #26 0xbffff478 in ?? () #27 0xbffff54c in ?? () #28 0xb7ec7940 in qsort () from /lib/tls/libc.so.6 Previous frame inner to this frame (corrupt stack?) (gdb) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-km Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages bsdutils depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an -- no debconf information -- ciao - Stefan
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm closing this since it seems to have been fixed before oldstable. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSc7wjAAoJEJrBOlT6nu75nG0IAIHTazmHQXY2cnZ4RPKNmuQR lDMGJWMXy2oJrrxv5zi2VYch1Xnrf8r7meQ0SrXQkwXDP4d3BB6+3XJ9LK+KdwPx ztsWdTWNQjK48hGukO2FFs9h4bT+Ge1G34mngvPgSuuaOT5soLaWtFfzagO23wSH SxCvakiOA0MJrFwDsQL14ev/VZTxYs4ln7v2UYS2ENEYnVl09UHPw+TcZArXtbBJ WrEeyIfHksIMdr9m6oL8BudX8JLrPsVhPwUjCxY3OVt/7UQfq37jq3fmc0gKox7s kZdVJRUzB2zAlhxAKHW9LRknZ6X+A6PF4eIpGY8QBsUgGhs3uhLmHgA5B0y5gKA= =unWV -----END PGP SIGNATURE-----
--- End Message ---
