26 Apr
2012
26 Apr
'12
1:01 p.m.
On 04/26/2012 01:20 AM, Timothy Pearson wrote:
OK,
We are making progress. I did get some debugging line number from qt3, but it
looks like I will have to rebuild tdelibs/tdebase again with more debug flags:
Reading symbols from /usr/lib/libpng15.so.15...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpng15.so.15
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /opt/tqt3/plugins/inputmethods/libqimsw-multi.so...done.
Loaded symbols for /opt/tqt3/plugins/inputmethods/libqimsw-multi.so
Reading symbols from /opt/tqt3/plugins/inputmethods/libqimsw-none.so...done.
Loaded symbols for /opt/tqt3/plugins/inputmethods/libqimsw-none.so
Reading symbols from /opt/tqt3/plugins/inputmethods/libqsimple.so...done.
Loaded symbols for /opt/tqt3/plugins/inputmethods/libqsimple.so
Reading symbols from /opt/tqt3/plugins/inputmethods/libqxim.so...done.
Loaded symbols for /opt/tqt3/plugins/inputmethods/libqxim.so
0x00007f236baffba8 in KateViewInternal::range(int, KateLineRange const*) ()
from /opt/trinity/lib/trinity/libkatepart.so
(gdb) bt
#0 0x00007f236baffba8 in KateViewInternal::range(int, KateLineRange const*) ()
from /opt/trinity/lib/trinity/libkatepart.so
#1 0x00007f236bb00b32 in KateViewInternal::range(unsigned int, int) ()
from /opt/trinity/lib/trinity/libkatepart.so
#2 0x00007f236bb024c9 in KateViewInternal::viewLineOffset(KateTextCursor
const&, int, bool) ()
from /opt/trinity/lib/trinity/libkatepart.so
#3 0x00007f236bb05d25 in KateViewInternal::makeVisible(KateTextCursor const&,
unsigned int, bool, bool, bool) () from /opt/trinity/lib/trinity/libkatepart.so
#4 0x00007f236bb06352 in KateViewInternal::updateCursor(KateTextCursor const&,
bool, bool, bool) ()
from /opt/trinity/lib/trinity/libkatepart.so
#5 0x00007f236bb0a4c0 in KateViewInternal::editEnd(int, int, bool) ()
from /opt/trinity/lib/trinity/libkatepart.so
#6 0x00007f236baa6ef0 in KateDocument::editEnd() () from
/opt/trinity/lib/trinity/libkatepart.so
#7 0x00007f236baa0f5b in KateDocument::paste(KateView*) () from
/opt/trinity/lib/trinity/libkatepart.so
#8 0x00007f236bad8a53 in KateView::paste() () from
/opt/trinity/lib/trinity/libkatepart.so
#9 0x00007f236bb08102 in KateViewInternal::mouseReleaseEvent(TQMouseEvent*) ()
from /opt/trinity/lib/trinity/libkatepart.so
#10 0x00007f2371866343 in TQWidget::event (this=0x1dc9490, e=0x7fff4a9f7740) at
kernel/qwidget.cpp:4725
#11 0x00007f23717d0559 in TQApplication::internalNotify (this=0x7fff4a9f7fe0,
receiver=0x1dc9490,
e=0x7fff4a9f7740) at kernel/qapplication.cpp:2638
#12 0x00007f23717cfbe3 in TQApplication::notify (this=0x7fff4a9f7fe0,
receiver=0x1dc9490, e=0x7fff4a9f7740)
at kernel/qapplication.cpp:2424
#13 0x00007f23727998c4 in KApplication::notify(TQObject*, TQEvent*) () from
/opt/trinity/lib/libtdecore.so.4
#14 0x00007f23717626b3 in TQApplication::sendSpontaneousEvent
(receiver=0x1dc9490, event=0x7fff4a9f7740)
at kernel/ntqapplication.h:526
#15 0x00007f237175bf53 in TQETWidget::translateMouseEvent (this=0x1dc9490,
event=0x7fff4a9f7c50)
at kernel/qapplication_x11.cpp:4380
#16 0x00007f2371759871 in TQApplication::x11ProcessEvent (this=0x7fff4a9f7fe0,
event=0x7fff4a9f7c50)
at kernel/qapplication_x11.cpp:3557
#17 0x00007f2371774c44 in TQEventLoop::processEvents (this=0x157c780, flags=4)
at kernel/qeventloop_x11.cpp:195
#18 0x00007f23717e3818 in TQEventLoop::enterLoop (this=0x157c780) at
kernel/qeventloop.cpp:201
#19 0x00007f23717e36e9 in TQEventLoop::exec (this=0x157c780) at
kernel/qeventloop.cpp:148
#20 0x00007f23717d0689 in TQApplication::exec (this=0x7fff4a9f7fe0) at
kernel/qapplication.cpp:2761
#21 0x00007f2374f3acf6 in kdemain () from /opt/trinity/lib/libtdeinit_kate.so
#22 0x000000000040082c in main ()
(gdb)
I'll open a bug report shortly :)
--
David C. Rankin, J.D.,P.E.
On 04/25/2012
11:08 PM, Calvin Morrison wrote:
Could be an Xorg glitch, an ABI problem in Xorg, or an indication of a
more serious problem in TDE. If you continue to experience problems after
rebuilding and reinstalling tqt3 a bug report will need to be filed with
detailed Xorg information from your system.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Err but if you're having problem getting line
numbers, you should enable
debugging with cmake flags. -DCMAKE_BUILD_TYPE i think it is and set it
to equal
DEBUG. that works for me at least.
Crud, I forgot all about that. I'll check. The x updates make sense. If
fonts
are rendering differently then some possible buffer overrun... Who knows,
but I
can't explain the hang causing kwrite CPU use to spike to nearly 90%. That
little app?