ttysnoops crashes with segmentation fault

Bug #250795 reported by Sakthivel
4
Affects Status Importance Assigned to Milestone
ttysnoop (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: ttysnoop

Source package: (Not sure)
    * ttysnoop_0.12d.orig.tar.gz (8.3 KiB)
    * ttysnoop_0.12d-3.diff.gz (7.2 KiB)
    * ttysnoop_0.12d-3.dsc (538 bytes)

1. System Release:
Description: Ubuntu 8.04.1
Release: 8.04

2. Version of Package:
ttysnoop:
  Installed: 0.12d-3
  Candidate: 0.12d-3
  Version table:
 *** 0.12d-3 0
        500 http://archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

3. Expected Result:
when invoking ttysnoops as a normal user,
$ttysnoops
ttysnoops should run smoothly or print any help/error message.

$ttysnoop 3
should clone the output of pts/3 terminal to its own pseudo terminal

4. Actual Result:
$ ttysnoops
can't bind server socket (/var/spool/ttysnoop/2)
                                                Segmentation fault
$ ttysnoop 3
can't connect to server
$ ttysnoop pty1
can't connect to server
$ ttysnoop pts1
can't connect to server
$ ttysnoop pts/1
can't connect to server
$

ProblemType: Bug
Architecture: i386
Date: Tue Jul 22 16:41:46 2008
Dependencies:
 libgcc1 1:4.2.3-2ubuntu7
 gcc-4.2-base 4.2.3-2ubuntu7
 libc6 2.7-10ubuntu3
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: fglrx
Package: ttysnoop 0.12d-3
PackageArchitecture: i386
ProcEnviron:
 PATH=/opt/BullseyeCoverage/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: ttysnoop
Uname: Linux 2.6.24-19-generic i686

Tags: apport-bug
Revision history for this message
JanBrinkmann (jbrinkmann) wrote :

Thanks you very much for reporting your problem. This helps to improve Ubuntu! I can confirm this behaviour on Intrepid i386 using ttysnoop 0.12d-3 . There is no package with debugging symbols available. Therefor, I'll attach a valgrind.log .

Changed in ttysnoop:
status: New → Confirmed
Revision history for this message
JanBrinkmann (jbrinkmann) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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