Hi Philippe,
sorry to be poking about this again. Is there any news on the issue? Can I
help to provide a fix for it? Would increasing the pool size really be a
good fix? Or should the code be re-written to dynamically allocate the
needed memory? I guess another solution could be to just truncate
Hi Philippe,
thanks a lot for your help. I have created this ticket
https://bugs.kde.org/show_bug.cgi?id=359133 to track the issue.
I was wondering, is there some kind out of out buffering when using printf
in valgrind? I guess that could explain why I do not see the debug print?
Thanks
/David
On Fri, 2016-02-05 at 11:20 +0100, David Hallas wrote:
> thanks for the reply. I tried increasing the SEGINFO_STRPOOLSIZE as
> you requested, and for me the magic number is 268*1024 then the assert
> goes away :) I also tried to add the print to the ML_(addStr) function
> in storage.c but for
Hi Philippe,
thanks for the reply. I tried increasing the SEGINFO_STRPOOLSIZE as you
requested, and for me the magic number is 268*1024 then the assert goes
away :) I also tried to add the print to the ML_(addStr) function in
storage.c but for some reason I never see the print?
I tried to play
On Thu, 2016-02-04 at 08:54 +0100, Florian Krohm wrote:
> On 03.02.2016 21:50, Philippe Waroquiers wrote:
> >
> > The assert might be caused by the debuginfo containing a string bigger
> > than SEGINFO_STRPOOLSIZE (64Kb).
>
> Why exactly are we having yet another fixed size buffer here?
> I've
On Wed, 2016-02-03 at 20:45 +0100, David Hallas wrote:
> valgrind: m_deduppoolalloc.c:258 (vgPlain_allocEltDedupPA): Assertion
> 'eltSzB <= ddpa->poolSzB' failed.
> I am running on a 64bit Linux system, and the binary is compiled using
> clang-3.7.
> Can anyone give some pointers as to what might
Hi Philippe,
thanks a lot for the quick reply!
I have rerun the test with -v -v -v -d -d -d options and attached the log.
I have also tested compiling the binary with gcc-5.2.1 and there I also see
the problem, so it doesn't look to be compiler specific.
If you have some specific patches you
On 03.02.2016 21:50, Philippe Waroquiers wrote:
>
> The assert might be caused by the debuginfo containing a string bigger
> than SEGINFO_STRPOOLSIZE (64Kb).
Why exactly are we having yet another fixed size buffer here?
I've spent a lot of time crawling through the code and getting rid of
those.
Hi All,
I have run into a problem with valgrind when analyzing a binary, I receive
the following error:
==19823== Memcheck, a memory error detector
==19823== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==19823== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright
