the
string, if it is just debug information then that would at least be better
that crashing?
Let me know how I can help
Thanks
/David
On Mon, Feb 8, 2016 at 2:19 PM, David Hallas <da...@davidhallas.dk> wrote:
> Hi Philippe,
>
> thanks a lot for your help. I have created this
On Fri, Feb 5, 2016 at 9:05 PM, Philippe Waroquiers <
philippe.waroqui...@skynet.be> wrote:
> 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 t
.
Thanks
/David
On Fri, Feb 5, 2016 at 12:53 AM, Philippe Waroquiers <
philippe.waroqui...@skynet.be> wrote:
> On Thu, 2016-02-04 at 08:28 +0100, David Hallas wrote:
> > Hi Philippe,
> >
> >
> > thanks a lot for the quick reply!
> >
> >
> > I
want tested, I can pull the valgrind
sources and do a local build?
Thanks for your help
/David
On Wed, Feb 3, 2016 at 9:50 PM, Philippe Waroquiers <
philippe.waroqui...@skynet.be> wrote:
> On Wed, 2016-02-03 at 21:33 +0100, Philippe Waroquiers wrote:
> > On Wed, 2016-02-03 at 20:
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
