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

List:       kde-bugs-dist
Subject:    [Bug 150931] need to remove remaining uses of Qt3Support container
From:       Germain Garand <germain () ebooksfrance ! com>
Date:       2007-10-20 16:39:43
Message-ID: 20071020163943.9010.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=150931         




------- Additional Comments From germain ebooksfrance com  2007-10-20 18:39 -------
> Have you tried valgrind? You may need to export KDE_DEBUG=1

thanks for that trick! without the export valgrind used to bail out with a memory \
error when I tried it with testregression. Now it works fine. I even just catched an \
invalid read in the html parser :)

> if (d->size == 0 || (node = *findNode(akey)) == e) { 
> return T(); 
..
> Try this if you're not convinced: 
> #include <iostream> 

aw enlightening... I was looking at that very bit of code yesterday, thinking, "now \
where in hell do they zero that memory?" ;(

> Your second assert looks dubious, though

yes, it looks like I misunderstood the API. Yet it is pretty illogical that a lookup \
directly returning a value wouldn't return the same result than a lookup followed by \
a value retrieval. I say the API is flawed! :)


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