kabl
10-28-2002, 07:12 PM
did a bt of my seg faults i seem to be seg faulting alot since i got latest cvs..
3 seg faults Back Traced (alot more not )all same here it is...
#0 0x0808a812 in EQPacket::decodePacket(int, unsigned char*) (this=0x82712d0,
size=46, buffer=0xbfffe41e "E") at packet.h:108
#1 0x0808a399 in EQPacket::processPackets() (this=0x82712d0) at packet.cpp:812
#2 0x0809577d in EQPacket::qt_invoke(int, QUObject*) (this=0x82712d0, _id=2,
_o=0xbfffea90) at m_packet.cpp:2146
#3 0x4024ed6b in QObject::activate_signal(QConnectionList*, QUObject*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#4 0x4024ec57 in QObject::activate_signal(int) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#5 0x40517b4b in QTimer::timeout() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#6 0x4026f792 in QTimer::event(QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#7 0x401fac49 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#8 0x401fa4f1 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#9 0x4019da88 in qt_activate_timers() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#10 0x4019b330 in QApplication::processNextEvent(bool) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#11 0x401fc280 in QApplication::enter_loop() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#12 0x4019b02d in QApplication::exec() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#13 0x080652d1 in main (argc=2, argv=0xbffff8f4) at main.cpp:937
#14 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
any ideas on this woudl rock )
edit - haha just looked at my post nice smily faces lol
edit#2 - ive been seeing alot of ppl complainign about these seg faults i see alot fo qt mumbojumbop up there this is with RH 8 and QT 3.05 btw maybe i shuld install 2.3.2? or are ppl haveing these issues with that too? or maybe these function can be made qt 3.05 freindly? or maybe im just grasping at straws :p lolol ive skimmed most the threads about seg faults and havent seen any answers yet......
3 seg faults Back Traced (alot more not )all same here it is...
#0 0x0808a812 in EQPacket::decodePacket(int, unsigned char*) (this=0x82712d0,
size=46, buffer=0xbfffe41e "E") at packet.h:108
#1 0x0808a399 in EQPacket::processPackets() (this=0x82712d0) at packet.cpp:812
#2 0x0809577d in EQPacket::qt_invoke(int, QUObject*) (this=0x82712d0, _id=2,
_o=0xbfffea90) at m_packet.cpp:2146
#3 0x4024ed6b in QObject::activate_signal(QConnectionList*, QUObject*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#4 0x4024ec57 in QObject::activate_signal(int) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#5 0x40517b4b in QTimer::timeout() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#6 0x4026f792 in QTimer::event(QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#7 0x401fac49 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#8 0x401fa4f1 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#9 0x4019da88 in qt_activate_timers() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#10 0x4019b330 in QApplication::processNextEvent(bool) ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#11 0x401fc280 in QApplication::enter_loop() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#12 0x4019b02d in QApplication::exec() ()
from /usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3
#13 0x080652d1 in main (argc=2, argv=0xbffff8f4) at main.cpp:937
#14 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
any ideas on this woudl rock )
edit - haha just looked at my post nice smily faces lol
edit#2 - ive been seeing alot of ppl complainign about these seg faults i see alot fo qt mumbojumbop up there this is with RH 8 and QT 3.05 btw maybe i shuld install 2.3.2? or are ppl haveing these issues with that too? or maybe these function can be made qt 3.05 freindly? or maybe im just grasping at straws :p lolol ive skimmed most the threads about seg faults and havent seen any answers yet......