[Ktechlab-devel] Ktechlab crash when drag and drop a component

[Julien Kroczek]

[Thread debugging using libthread_db enabled]
[New Thread 0x7f0b784e1700 (LWP 13367)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f0b784e1700 (LWP 13367)]
0x00000000006670ac in Map::reset (this=0xde5280) at matrix.cpp:308
308                             (*m_map)[i][j] = 0;

(gdb) backtrace
#0  0x00000000006670ac in Map::reset (this=0xde5280) at matrix.cpp:308
#1  0x0000000000667ab8 in Map (this=0xde5280, size=2) at matrix.cpp:292
#2  0x0000000000668599 in Matrix (this=0xddea10, n=1, m=1) at
matrix.cpp:35
#3  0x0000000000664c18 in ElementSet (this=0xdec870, circuit=0xde6910,
n=1,
    m=1) at elementset.cpp:32
#4  0x000000000065d315 in Circuit::init (this=0xde6910) at
circuit.cpp:203
#5  0x000000000050d65b in CircuitDocument::assignCircuits
(this=0xd0b8d0)
    at circuitdocument.cpp:472
#6  0x000000000050f2a5 in CircuitDocument::qt_invoke (this=0xd0b8d0,
_id=47,
    _o=0x7fff80523090) at circuitdocument.moc:142
#7  0x00007f0b71526daf in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#8  0x00007f0b71529122 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00007f0b71547595 in QTimer::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#10 0x00007f0b714c8435 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00007f0b714c921a in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00007f0b72af2972 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#13 0x00007f0b714be9fe in QEventLoop::activateTimers ()
....

Le vendredi 25 juillet 2008 à 19:46 +0200, Zoltan Padrah a écrit :
> 
> 2008/7/25, julien kroczek <julien.kroczek at gmail.com>:
>         Hello,
>         
>         This is what i get when I drag and drop a component on a empty
>         circuit :
>         
>          [?1034h(no debugging symbols found)
>         (no debugging symbols found)
>         
>         
>         It's on a suse 11.0 64 bits with kde 3 or 4
>         Thanks a lot!
>         
> 
> 
>  Could you please also tell the exact version of ktechlab you are
> using? 
> 
>  Another problem is that there are no debug symbols, so it's hard to tell from that stack trace where has the program crashed. A debug version would be of bigger use.