[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: How to debug kioslave problems ? [Was: Problem opening
From:       Pavel Troller <patrol () sinus ! cz>
Date:       2006-04-03 19:41:50
Message-ID: 20060403194150.GA26495 () tangens ! sinus ! cz
[Download RAW message or body]

> Pavel Troller wrote:
> >  Immediately after the slave started, the dialog with "Malformed URL"
> >appeared in konq. However, the slave continued to run and when
> > Ctrl-C'ed, it showed it's idling in its KIO:SlaveBase:DispatchLoop().
> > There were no messages output by the slave.
> 
> You probably want to set a breakpoint in stat() or listDir() or get() (or 
> all three) to catch the Konqueror request.
> 
Hi!
  many thanks to all of you, I've made a substantial progress!
  Now I know, why it doesn't work:
  bluetooth slave doesn't implement get() at all! All the implementaion
consists of

void KioBluetooth::get(const KURL &/*url*/)
{
    kdDebug() << "kio_bluetooth: get() was called! This is nonsense." << endl ;
    error(KIO::ERR_IS_DIRECTORY, QString::null);
}

  After checking debug class 0 and putting breakpoints to all of the functions,
I've got the result by two ways simultaneously :-).

  But... It WORKED formerly! It still works on KDE3.5.1, installed on my
notebook. It was not a dream, it was a reality :-). According to svn log,
kiobluetooth.cpp was not touched since the package was created in SVN. So
probably, there was a recent change in kioslave handling, which caused that
now get() is being used and formerly it probably wasn't.
  What to do next ? Is it necessary to write a real get(), or could it be
possible to omit its call for kio_bluetooth, as it used to be ? 

                   With regards, Pavel Troller
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]