wish8.5 crashed with SIGSEGV in strcmp() [amsn]

Bug #445742 reported by Misha
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
tk8.5 (Ubuntu)
New
Medium
Unassigned

Bug Description

Description: Ubuntu karmic (development branch)
Release: 9.10

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 7 23:23:17 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/wish8.5
NonfreeKernelModules: fglrx
Package: tk8.5 8.5.7-1
ProcCmdline: wish8.5 /usr/bin/amsn
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x7f2f6c1c1e20 <strcmp>: mov (%rdi),%al
 PC (0x7f2f6c1c1e20) ok
 source "(%rdi)" (0x2535343035313232) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: tk8.5
StacktraceTop:
 strcmp () from /lib/libc.so.6
 ?? () from /usr/lib/tcltk/snack2.2/libsnack.so
 ?? () from /usr/lib/libtcl8.5.so.0
 Tcl_ServiceEvent () from /usr/lib/libtcl8.5.so.0
 Tcl_DoOneEvent () from /usr/lib/libtcl8.5.so.0
Title: wish8.5 crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Misha (mishailpetrov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strcmp () at ../sysdeps/x86_64/strcmp.S:29
?? () from /usr/lib/tcltk/snack2.2/libsnack.so
TimerHandlerEventProc (evPtr=<value optimized out>,
Tcl_ServiceEvent (flags=-3)
Tcl_DoOneEvent (flags=-3)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
affects: ubuntu → tk8.5 (Ubuntu)
Changed in tk8.5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
security vulnerability: yes → no
visibility: private → public
summary: - wish8.5 crashed with SIGSEGV in strcmp()
+ wish8.5 crashed with SIGSEGV in strcmp() [amsn]
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.