Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 93199

Summary: kde-base/kdat-3.4.0: sigfpe after completing a backup.
Product: Gentoo Linux Reporter: Jason McGuiness <gentoo-bugs>
Component: New packagesAssignee: Gentoo KDE team <kde>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Jason McGuiness 2005-05-19 05:51:35 UTC
When a backup is apparently completed, a sigfpe signal is caught, causing kdat 
to crash.

Reproducible: Always
Steps to Reproduce:
1. Mounting a tape. (See bug 93194.)
2. Select some files to backup.
3. Back them up.
4. The backup dialog will appear, showing files being written. (The tape drive 
makes noises and shows activity.)
5. Once all of the files are written, an dialog appears stating that "sigfpe" 
has been caught and the program has crashed.
Actual Results:  
An error dialog appeared saying that a sigfpe was caught.

Expected Results:  
The backup should have completed.

Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-
gentoo-r7 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r7 x86_64 AMD Opteron(tm) Processor 250
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, May 15 2005, 23:35:44)]
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.59-r6
sys-devel/automake:  1.9.5, 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6
sys-devel/binutils:  2.15.92.0.2-r8
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=opteron -O0 -pipe -g"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /
var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=opteron -O0 -pipe -g"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distcc distlocks nostrip sandbox strict"
GENTOO_MIRRORS="http://gentoo.mirror.sdv.fr http://ftp.easynet.nl/mirror/gentoo/ http://
www.gigaload.org/gentoo.org/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/
distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/dev/shm/portage/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X aalib acpi alsa amd64 bash-completion berkdb bitmap-fonts bzlib cdr crypt cups curl 
dvd dvdread exif fam flac font-server foomaticdb gdbm gif gpm gtk gtk2 imagemagick imlib 
ipv6 jp2 jpeg libwww lm_sensors lzw lzw-tiff mad motif mp3 ncurses network nls nptl 
nptlonly ogg oggvorbis opengl pam pda perl png ppds python qt qtmt readline rtc sdk spell 
ssl sysfs tcpd tetex threads tiff truetype truetype-fonts type1-fonts usb userlocales 
vorbis xfce4 xine xml xml2 xmms xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 1 Jason McGuiness 2005-05-19 05:54:00 UTC
I ran kdat, after rebuilding it with "-O0 -g" and nostrip, from gdb and got a 
stack trace:

> gdb kdat
GNU gdb 6.3
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 "x86_64-pc-linux-gnu"...Using host libthread_db 
library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/kde/3.4/bin/kdat
[Thread debugging using libthread_db enabled]
[New Thread 46912560819184 (LWP 26767)]
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
kbuildsycoca running...
DCOP Cleaning up dead connections.
tar: Semantics of -l option will change in the future releases.
tar: Please use --one-file-system option instead.

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 46912560819184 (LWP 26767)]
0x000000000041a2d8 in BackupDlg::slotProcessExited (this=0x7fffffffdab0)
    at BackupDlg.cpp:298
298     BackupDlg.cpp: No such file or directory.
        in BackupDlg.cpp
(gdb) where
#0  0x000000000041a2d8 in BackupDlg::slotProcessExited (this=0x7fffffffdab0)
    at BackupDlg.cpp:298
#1  0x00000000004177b8 in BackupDlg::qt_invoke (this=0x7fffffffdab0, _id=50,
    _o=0x7fffffffd280) at BackupDlg.moc:104
#2  0x00002aaaac53bae8 in QObject::activate_signal ()
   from /usr/qt/3/lib/libqt-mt.so.3
#3  0x00002aaaab8795f6 in KProcess::processExited ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#4  0x00002aaaab87cd68 in KProcessController::slotDoHousekeeping ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#5  0x00002aaaab87cdcc in KProcessController::qt_invoke ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#6  0x00002aaaac53bae8 in QObject::activate_signal ()
   from /usr/qt/3/lib/libqt-mt.so.3
#7  0x00002aaaac53c0ef in QObject::activate_signal ()
   from /usr/qt/3/lib/libqt-mt.so.3
#8  0x00002aaaac5543ab in QSocketNotifier::event ()
   from /usr/qt/3/lib/libqt-mt.so.3
#9  0x00002aaaac4e2fbd in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#10 0x00002aaaac4e3340 in QApplication::notify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#11 0x00002aaaab82d202 in KApplication::notify ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#12 0x00002aaaac4d81bf in QEventLoop::activateSocketNotifiers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#13 0x00002aaaac499201 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#14 0x00002aaaac4f70c5 in QEventLoop::enterLoop ()
   from /usr/qt/3/lib/libqt-mt.so.3
#15 0x00002aaaac6999d4 in QDialog::exec () from /usr/qt/3/lib/libqt-mt.so.3
#16 0x000000000042dd14 in KDat::fileBackup (this=0x710390) at KDat.cpp:523
#17 0x0000000000428edc in KDat::qt_invoke (this=0x710390, _id=78,
    _o=0x7fffffffdf50) at KDat.moc:161
#18 0x00002aaaac53bae8 in QObject::activate_signal ()
   from /usr/qt/3/lib/libqt-mt.so.3
#19 0x00002aaaac81ed26 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3
#20 0x00002aaaac55240d in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3
#21 0x00002aaaac6296a1 in QPopupMenu::mouseReleaseEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#22 0x00002aaaac56dce9 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#23 0x00002aaaac4e2fbd in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#24 0x00002aaaac4e34ee in QApplication::notify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#25 0x00002aaaab82d202 in KApplication::notify ()
   from /usr/kde/3.4/lib/libkdecore.so.4
#26 0x00002aaaac489043 in QETWidget::translateMouseEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#27 0x00002aaaac487d18 in QApplication::x11ProcessEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#28 0x00002aaaac498b0b in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#29 0x00002aaaac4f70c5 in QEventLoop::enterLoop ()
   from /usr/qt/3/lib/libqt-mt.so.3
#30 0x00002aaaac4f7022 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#31 0x0000000000452844 in main (argc=1, argv=0x7fffffffee98) at main.cpp:95
(gdb)
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2005-05-30 13:01:58 UTC
While not exactly a dupe, Gregorio is right regarding kdat. There didn't
happened anything in cvs for a long time.

*** This bug has been marked as a duplicate of 93194 ***