Bug 60485 - setup scanning for channel and crash - SuSE 8.2
Summary: setup scanning for channel and crash - SuSE 8.2
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwintv
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWinTV Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-29 12:21 UTC by john
Modified: 2003-10-24 01:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description john 2003-06-29 12:21:55 UTC
Version:           0.8.12 CVS (using KDE 3.1.1)
Installed from:    SuSE
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.20-64GB-SMP

As soon as I start the WIZARD (scan whole frequency band) the KWINTV crashes.
If I select manually the frequency range, I don't find any channel.
Hereunder the dump :

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 7336)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40f27cf7 in waitpid () from /lib/libpthread.so.0
#0  0x40f27cf7 in waitpid () from /lib/libpthread.so.0
#1  0x40640c89 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x40f26895 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x080c2081 in QMemArray<QRect>::detach() ()
#5  0x080c7d1e in QMemArray<QRect>::detach() ()
#6  0x080c2a70 in QMemArray<QRect>::detach() ()
#7  0x409cc8e7 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#8  0x409cc78f in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3
#9  0x40cca3ec in QButton::clicked() () from /usr/lib/libqt-mt.so.3
#10 0x40a54716 in QButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/libqt-mt.so.3
#11 0x40a02954 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#12 0x4096b5f8 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#13 0x4096ad76 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#14 0x405cd929 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x4090c5c8 in QETWidget::translateMouseEvent(_XEvent const*) ()
   from /usr/lib/libqt-mt.so.3
#16 0x40909e30 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/libqt-mt.so.3
#17 0x4091f4f2 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/libqt-mt.so.3
#18 0x4097fb83 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#19 0x4097fa76 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#20 0x4096b87f in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#21 0x0807db3a in QMemArray<char>::detach() ()
#22 0x410858ae in __libc_start_main () from /lib/libc.so.6

I have Checked the Haupauge board under Windows XP, it works fine.
I hope those info will be sufficent

Best regards,
John
Comment 1 George Staikos 2003-10-24 01:59:15 UTC
Sorry folks, we're only fixing bugs in the rewrite, which is unfortunately coming along 
very slowly.  The old code is very buggy and dangerous to change without breaking 
many many things.