Another error with KDE 3.3

Hi,
I've now run into another build error against KDE 3.3, this
time in debugger 
code. I'm making use of the KListViewSearchLineWidget, and
it's only 
available since KDE 3.4. This time, I don't know about any
easy workaround, 
it's only possible to rewrite that widget completely, which
I'd rather not 
do.

Ideas?

- Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Wednesday 24 May 2006 11:33, Vladimir Prus wrote:
> Hi,
> I've now run into another build error against KDE 3.3,
this time in
> debugger code. I'm making use of the
KListViewSearchLineWidget, and
> it's only available since KDE 3.4. This time, I don't
know about any
> easy workaround, it's only possible to rewrite that
widget
> completely, which I'd rather not do.
>
> Ideas?

As it was stated the first decision was to require KDE 3.4.
You could 
try the following:
- #ifdef out the KListViewSearchLineWidget parts, so this
will be 
missing in KDE 3.3.
- import KListViewSearchLineWidget sources into
kdevelop/lib/compat and 
compile /use if KDE < 3.4.
- don't do anything, and KDevelop 3.4 will require KDE 3.4.

Certainly don't spend time to rewrite the code.

Andras
-- 
Quanta Plus developer - http://quanta.kdewebdev.o
rg
K Desktop Environment - http://www.kde.org
_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

Hi! I still occassionally get the same crash we once talked
about. The only 
difference is that it doesn't happen that often.

Here is a backtrace:

Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241733440 (LWP 23382)]
[New Thread -1258050640 (LWP 24820)]
[KCrash handler]
#6  0x00000026 in ?? ()
#7  0xb50f52a0 in GDBDebugger::GDBCommand::invokeHandler
(this=0xda6a0f0, 
    r=0x9bb6f18) at gdbcommand.cpp:36
#8  0xb50f0a9e in
GDBDebugger::GDBController::processMICommandResponse (
    this=0xce96fa8, result=0x9bb6f18) at
gdbcontroller.cpp:1386
#9  0xb50f1114 in GDBDebugger::GDBController::slotDbgStdout
(this=0xce96fa8, 
    buf=0xbfd29f17 "^done\n(gdb) \n",
buflen=13) at gdbcontroller.cpp:1527
#10 0xb50ecf60 in GDBDebugger::GDBController::qt_invoke
(this=0xce96fa8, 
    _id=44, _o=0xbfd29e8c) at gdbcontroller.moc:254
#11 0xb67d4929 in QObject::activate_signal (this=0xd93fc10,
clist=0xda857b0, 
    o=0xbfd29e8c) at kernel/qobject.cpp:2355
#12 0xb6e2d65f in KProcess::receivedStdout () from
/usr/lib/libkdecore.so.4
#13 0xb6e2d829 in KProcess::childOutput () from
/usr/lib/libkdecore.so.4
#14 0xb6e2d861 in KProcess::slotChildOutput () from
/usr/lib/libkdecore.so.4
#15 0xb6e2dcf3 in KProcess::qt_invoke () from
/usr/lib/libkdecore.so.4
#16 0xb67d4929 in QObject::activate_signal (this=0xa6f8b60,
clist=0xc338d20, 
    o=0xbfd2a428) at kernel/qobject.cpp:2355
#17 0xb67d5238 in QObject::activate_signal (this=0xa6f8b60,
signal=2, 
    param=46) at kernel/qobject.cpp:2448
#18 0xb6b34c67 in QSocketNotifier::activated
(this=0xa6f8b60, t0=46)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#19 0xb67f4faa in QSocketNotifier::event (this=0xa6f8b60,
e=0xbfd2a770)
    at kernel/qsocketnotifier.cpp:258
#20 0xb676bf80 in QApplication::internalNotify
(this=0xbfd2a9ec, 
    receiver=0xa6f8b60, e=0xbfd2a770) at
kernel/qapplication.cpp:2635
#21 0xb676c172 in QApplication::notify (this=0xbfd2a9ec,
receiver=0xa6f8b60, 
    e=0xbfd2a770) at kernel/qapplication.cpp:2358
#22 0xb6ed317c in KApplication::notify () from
/usr/lib/libkdecore.so.4
#23 0xb7d451dc in QApplication::sendEvent
(receiver=0xa6f8b60, 
    event=0xbfd2a770) at qapplication.h:491
#24 0xb675dacb in QEventLoop::activateSocketNotifiers
(this=0x8140c50)
    at kernel/qeventloop_unix.cpp:578
#25 0xb6710a60 in QEventLoop::processEvents (this=0x8140c50,
flags=4)
    at kernel/qeventloop_x11.cpp:383
#26 0xb6783cfb in QEventLoop::enterLoop (this=0x8140c50)
    at kernel/qeventloop.cpp:198
#27 0xb6783c1e in QEventLoop::exec (this=0x8140c50)
    at kernel/qeventloop.cpp:145
#28 0xb676ac13 in QApplication::exec (this=0xbfd2a9ec)
    at kernel/qapplication.cpp:2758
#29 0x0804ebba in main (argc=1, argv=0xbfd2ac34) at
main.cpp:145


greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel

On Friday 26 May 2006 07:30, David Nolden wrote:
> Hi! I still occassionally get the same crash we once
talked about. The only
> difference is that it doesn't happen that often.
>
> Here is a backtrace:

Can you provide me with debug output from KDevelop, as
described in

   http://lists.kde.org/?l=kdevelop-devel&m
=114827903518277&w=2

? The thing is, I probably can plaster this problem right
now, but I want to 
know for sure why this happens.

BTW, does this happens when you remove breakpoint by the
click in the editor, 
or when deleting via breakpoint window?

Thanks,
Volodya

_______________________________________________
KDevelop-devel mailing list
KDevelop-develbarney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/
kdevelop-devel