Beta binary

[Lubomir I. Ivanov]

On 28 November 2013 22:48, Thiago Macieira <thiago at macieira.org> wrote:
> On quinta-feira, 28 de novembro de 2013 11:29:07, Linus Torvalds wrote:
>> but I get a *lot* or warnings from valgrind deep in Qt. Most of them
>> seem to be about 4-byte accesses that go past the end of a string,
>> which is almost certainly the usual "somebody just optimized a string
>> function to work a word at a time" issue. I think Thiago at some point
>> said that SuSE had better annotations for some of these things.
>
> Can you share what those were? I know strlen, strcmp, the mem versions are
> optimised in glibc to use word-at-a-time (or more, using SSE2) if the
> processor can do it. Also, GCC often does exactly that for the built-ins it
> inserts into the code.
>
> Unfortunately, valgrind is at odds with the compiler. Any aligned load
> containing at least one valid byte cannot segfault, so it's valid to do that
> provided you don't act on any bytes past the end of your buffer.
>

thiago, would you appreciate a "dr.memory" log as well?
it has been considered as one of the best valgrind alternatives for
win32, if not even better.

i can draw this one in a flash if you say so, but not sure how helpful
it will be...
before we switched to Qt most of my memory leak "work" for subsurface
was mainly based around those reports.

i even found a bug in the tool itself...

lubomir
--