Re: [Valgrind-users] Invalid read of size 1

2020-06-07 Thread James Read
On Sun, Jun 7, 2020 at 4:16 PM Derrick McKee wrote: > It looks like you're using a pointer that has been freed some time earlier. > Yeah. Thanks. > > On Sun, Jun 7, 2020, 10:52 James Read wrote: > >> I'm getting a series of Invalid read of size 1 errors. These seem to be >> related to strlen(

Re: [Valgrind-users] Invalid read of size 1

2020-06-07 Thread Derrick McKee
It looks like you're using a pointer that has been freed some time earlier. On Sun, Jun 7, 2020, 10:52 James Read wrote: > I'm getting a series of Invalid read of size 1 errors. These seem to be > related to strlen() calls. How is it possible for strlen() to make an > invalid read? > > Here is m

[Valgrind-users] Invalid read of size 1

2020-06-07 Thread James Read
I'm getting a series of Invalid read of size 1 errors. These seem to be related to strlen() calls. How is it possible for strlen() to make an invalid read? Here is my valgrind output: ==21737== Invalid read of size 1 ==21737==at 0x483EF46: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgprelo