Valgrind hit in kio_data [PATCH]

[George Staikos]

On Thursday 24 February 2005 18:14, André Wöbbeking wrote:
> On Friday 25 February 2005 00:05, David Faure wrote:
> > Starting kmail and selecting a mail from Till (whose photo I have in
> > my addressbook, against my will, I guess it's part of that kdepim
> > vcard I was tricked into downloading) leads to an invalid read in KIO
> > due to kio_data.
>
> I sent something similar to kdepim (Valgrind meets Kontact, 29.01.05):
>
> Invalid read of size 1
>    at 0x43AC4C49: KIO::TransferJob::start(KIO::Slave*) (job.cpp:1086)
>  Address 0x35E55148 is 216 bytes inside a block of size 284 free'd
>    at 0x3414CCFA: operator delete(void*) (vg_replace_malloc.c:156)
>    by 0x43ACBA29: KIO::TransferJob::~TransferJob() (job.cpp:1161)

[...]


> Invalid read of size 4
>    at 0x451EFE50: KMMoveCommand::execute() (kmmsgbase.h:126)
>    by 0x9C5FD9DF: ???
>  Address 0x356B265C is 4 bytes inside a block of size 32 free'd
>    at 0x3414CCFA: operator delete(void*) (vg_replace_malloc.c:156)
>    by 0x450AEB17: KMMsgInfo::~KMMsgInfo() (kmmsginfo.cpp:131)
>
> without any photos. But no one replied.

   This one is unrelated to the above, and I have it fixed locally, but it now 
triggers more crashes elsewhere.  There are invalid pointers all over the 
place.  I'm testing more fixes now.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/