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

List:       kde-core-devel
Subject:    Re: kio problem
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-02-25 14:35:04
[Download RAW message or body]

This looks like a kdebug problem.
(Note the <area string>: before the garbage)

'somebody' broke the standard version of kDebug while hacking
kdDebug :-)

On Fri, Feb 25, 2000 at 03:46:00PM +0100, Simon Hausmann wrote:
> Hi,
> 
> I just compiled kdelibs/kdebase fresh and now strange things happen:
> 
> alister:~$ konqueror
> DCOPClient: setup DCOP protocol. Major opcode = 2
> kio (KMimeType): .
> p?t?l?
> Segmentation fault
> 
> kioslavetest gives similar "results":
> listing /tmp , containing one single file:
> 
> [..]
> kio (KIOConnection): read
> kio (KIOConnection): read cmd 107
> kio (KIOConnection): finished reading cmd 107
> kio (KIOJob): dispatch 107
> kioslavetest: 
>              P
>              4|@PTI@lo@
>                       0?
> @                        t?>
> 
> kioslavetest: p
>               L
>               4|@PTI@lo@x
>                         0?x
>                             t?PI
> [..etc etc..]
> 
> Any ideas?
> 
> Ciao,
>  Simon
> 
> P.S.: same results with updated libkio, including coolo's latest
>       QDataStream operator fix (dunno if that's related)

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

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