tkdesksh crashed with SIGSEGV in TclInvokeStringCommand()

Bug #375504 reported by dj5qy
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tcl8.4 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: tkdesk

jaunty, kubuntu 9.04, crashes when processing tkdesksh and reports Segmentation fault in konsole where i started tkdesk

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0x0:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/tkdesk/tkdesksh
Package: tkdesk 2.0-9
ProcCmdline: /usr/lib/tkdesk/tkdesksh /usr/bin/tkdesk
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
Signal: 11
SourcePackage: tkdesk
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libBLT.2.4.so.8.4
 ?? () from /usr/lib/libBLT.2.4.so.8.4
 TclInvokeStringCommand () from /usr/lib/libtcl8.4.so.0
 ?? () from /usr/lib/libtcl8.4.so.0
Title: tkdesksh crashed with SIGSEGV in TclInvokeStringCommand()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio bin cdrom daemon dialout dip disk fax floppy fuse haldaemon libuuid lp lpadmin plugdev polkituser pulse pulse-access pulse-rt root scanner sudo sys syslog tty users uucp video

Revision history for this message
dj5qy (ulf-schreglmann) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
HoldOp (clientData=0x8206fc8, interp=0x8162710, argc=4,
BusyCmd (clientData=0x8206fc8, interp=0x8162710, argc=5,
TclInvokeStringCommand (clientData=0x8207048,
InvokeImportedCmd (clientData=0x8285db0, interp=0x8162710,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in tkdesk (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
affects: tkdesk (Ubuntu) → tcl8.4 (Ubuntu)
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in tcl8.4 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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