Ubuntu
bash package

[apport] clear_console crashed with SIGSEGV in strlen()

Bug #89686 reported by Sebastian Schack on 2007-03-04

This bug report is a duplicate of: Bug #87402: [apport] clear_console crashed with SIGSEGV in strlen(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	bash (Ubuntu)	In Progress	Medium	Unassigned

Bug Description

Binary package hint: bash

Crash occured right after the first boot after the installation.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 4 18:12:02 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/clear_console
Package: bash 3.2-0ubuntu4
ProcCmdline: /usr/bin/clear_console -q
ProcCwd: /home/sebastian
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=de_DE.UTF-8
Signal: 11
SourcePackage: bash
Stacktrace:
#0 0xb7de7c03 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0x080488f4 in ?? ()
#2 0x00000000 in ?? ()
StacktraceTop:
strlen () from /lib/tls/i686/cmov/libc.so.6
?? ()
?? ()
ThreadStacktrace:
.
Thread 1 (process 6656):
#0 0xb7de7c03 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0x080488f4 in ?? ()
#2 0x00000000 in ?? ()
Uname: Linux earth 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

Sebastian Schack (sschack) wrote on 2007-03-04:

Dependencies.txt Edit (445 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (736 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (673 bytes, text/plain; charset="utf-8")
Registers.txt Edit (444 bytes, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-03-10:

Thank you for your bug

Changed in bash:
importance:	Undecided → Medium
status:	Unconfirmed → In Progress

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-03-10:

Debug backtrace for the crash:

#0 0xb7de7c03 in ?? ()
#1 0x080488f4 in is_pseudo_tty (fd=0) at debian/clear_console.c:149
        tty = 0x0
#2 0x080489c1 in clear_console (fd=3) at debian/clear_console.c:168
        num = <value optimized out>
        tmp_num = <value optimized out>
        vtstat = {v_active = 49132, v_signal = 53480, v_state = 49132}
#3 0x08048dc4 in main (argc=2, argv=0xbfecd1c4) at debian/clear_console.c:259
        fd = <value optimized out>
        result = 0
        an_option = -1074998832
#4 0xb7d8febc in ?? ()
#5 0x00000002 in ?? ()
#6 0xbfecd1c4 in ?? ()
#7 0xbfecd1d0 in ?? ()
#8 0xb7f29898 in ?? ()
#9 0x00000000 in ?? ()
--- thread stack trace ---
.
Thread 1 (process 6656):
#0 0xb7de7c03 in ?? ()
#1 0x080488f4 in is_pseudo_tty (fd=0) at debian/clear_console.c:149
        tty = 0x0
#2 0x080489c1 in clear_console (fd=3) at debian/clear_console.c:168
        num = <value optimized out>
        tmp_num = <value optimized out>
        vtstat = {v_active = 49132, v_signal = 53480, v_state = 49132}
#3 0x08048dc4 in main (argc=2, argv=0xbfecd1c4) at debian/clear_console.c:259
        fd = <value optimized out>
        result = 0
        an_option = -1074998832
#4 0xb7d8febc in ?? ()
#5 0x00000002 in ?? ()
#6 0xbfecd1c4 in ?? ()
#7 0xbfecd1d0 in ?? ()
#8 0xb7f29898 in ?? ()
#9 0x00000000 in ?? ()